• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Java date questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Java date questions


  • Subject: Re: Java date questions
  • From: Eric Hermanson <email@hidden>
  • Date: Thu, 30 Oct 2003 09:23:54 -0800

On Oct 30, 2003, at 8:17 AM, email@hidden wrote:

Man, this stuff is so confusing.  It's not really WO's fault;  Java is
confusing enough when dealing with date/times already.  But adding one
extra class (NSTimestamp) on to everything else doesn't help much.

I second that sentiment, but I think it's even worse than that. The real problem originated with the original JDBC specification. For some reason, (Sun?) decided that it was wise to subclass java.util.Date in order to override a single "toString" method that formats the date into an SQL "escape" format string. This means that everyone is forced to use baloney subclasses (java.sql.Date and java.sql.Timestamp) when working with the database. Obviously, the JDBC adaptor should accept standard java.util.Date objects and perform any necessary conversions internally. Haven't these guys ever heard of DELEGATES?! :)


- Eric
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

References: 
 >Re: Java date questions (From: email@hidden)

  • Prev by Date: Re: Java version Hot Spot
  • Next by Date: RE: Java version Hot Spot
  • Previous by thread: Re: Java date questions
  • Next by thread: Re: Java date questions
  • Index(es):
    • Date
    • Thread