On Sep 30, 2010, at 12:03 AM, Simon wrote: >> Calendar dates should not be represented by NSTimestamp. The Date prototype >> is wrong for using it IMHO. > > i couldn't agree more. but where do we go from here ? > > 1) leave the mysql date prototype as it is now, broken and unusable
If it is broken, then either no one is using it, or they are using it in a way that your change would break. > 2) patch the mysql date prototype so that it works properly, but still > mapped to NSTimestamp so that we don't break everyone in the world who > is using it as an NSTimestamp > > 3) change the mysql date prototype completely (i'm a fan of plain old > int's) and put up with the flack from the people we break! > > 4) alternatively i guess we could just add a new mysql prototype (e.g. > intDate) .... ? Why ints? If we are going to do that, why not find a Java class that gives us what we really want? Or, uh, what we think we want. Chuck -- Chuck Hill Senior Consultant / VP Development Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems. http://www.global-village.net/products/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
