RE: New FormType

Hi Jake!

I think the persistence coupling here is more appearance than reality. The
bottom line (IMO) is that FormType is all about making it really easy to
transform URL String data to first class data objects which the business
domain needs to work with.

Now, if you happen to be using DB apps, Timestamp happens to be a very handy
first class object (and the fact that its in java.sql rather than java.lang
is really just a function of the way it worked out in
practice...functionaly, timestamp is really just a first class data type
like all the others in java.util...it's not actually coupled to the notion
of DB's per se; it just happens to get used there a lot).

SO...its a very useful data type to support, and its part of the standard
JDK since at least 1.3, therefore...I don't see any reason NOT to include it
in FormType. That is what its for after all... Plus, it doesn't break
anything or cause any real inconvenience...its just added functionality
(which we really needed, and I suspect other people will find very useful
too).

My .02...
Christian
----------------------------------------------
Christian Cryder [[email protected]]
Internet Architect, ATMReports.com
Barracuda - http://barracudamvc.org
----------------------------------------------
"Coffee? I could quit anytime, just not today"

  -----Original Message-----
  From: [email protected]
[mailto:[email protected]]On Behalf Of Jacob Kjome
  Sent: Thursday, May 15, 2003 8:05 PM
  To: [email protected]
  Subject: Re: [Barracuda] New FormType



  Hmm... I'm not sure about this?  Why should the FormType class have
anything to do with SQL?  It assumes the storage device; a relational
database.  FormType should not be doing this.  It should be storage device
agnostic and deal with general java objects/datatypes.

  Does anyone feel the same way, or am I just being pedantic?

  Jake

  At 04:37 PM 5/15/2003 -0400, you wrote:

    Hey folks,

    Just an FYI...there is now a new form mapping type called
FormType.TIMESTAMP
    (java.sql.Timestamp).

    Basically, what it will do is handle either time values (represented as
a
    long) or date values (ie. entered by a user), and convert both of them
to a
    java.sql.Timestamp value that can be shoved directly back into a db
(whereas
    java.util.Date cannot).

    Just thought you might want to know...

    Christian

    ----------------------------------------------
    Christian Cryder [[email protected]]
    Internet Architect, ATMReports.com
    Barracuda - http://barracudamvc.org
    ----------------------------------------------
    "Coffee? I could quit anytime, just not today"

    _______________________________________________
    Barracuda mailing list
    [email protected]
    http://barracudamvc.org/lists/listinfo/barracuda