I think we should stick with the existing syntax for using SimpleDateFormat
since that is what people already know, I can't think of a powerful reason
to not stick with it.
Agreed.
I like the preset patterns in DateUtils like ISO8601_TIME_PATTERN, however,I agree that the ISO patterns are nice. We probaly want another few hard-coded formats and the ability to add more as you say. Perhaps we could have a static method for adding a custom format that would be available from then on out through another static method for formating using the custom format.
I also wish that there was a way to register new patterns globally.
I workYeah we should probably resist the temptation to make this too specialized. Using the custom methods you could achieve the same thing by making the SQL server a constant in your code and then use the custom methods. Deciding which formats make it into DateUtils will be a bit sticky (I predict.)
with MSSQL Server, and have to convert their pattern a lot: 2002-12-12
23:25:29.93. However, I guess we wouldn't want to dump in a million
patterns into the core code base.
- sean
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>