On 1 September 2001 09:27, you wrote:
> Fedor Karpelevitch <[EMAIL PROTECTED]> writes:
> > 1) implemented Gonzalo's suggestion to use JDBC escapes for dates. Seems
> > to work well and solves all the inherent problems with dates.
>
> Forward ported to jakarta-turbine-3 into SqlExpression and DB.
> SqlExpression relies on DB to do the formatting, so I slapped the
> escape in as the default formatting mechanism (i.e. the toDateString()
> method).
I do not think toDateString() is needed at all since JDBC escape should work
fine for *any* database. I think it can be dropped (deprecated first).
fedor.
>
> John, if you have a moment to look over this change, I'd appreciate
> it.
>
> > 2) reverted my change to DateKey.toString() - it was an attempt to solve
> > the problem above, but did not work out very well. With the fix above it
> > is no longer needed, and it was causing inconsistent behaviour -
> > toString() results were different depending on the history of the
> > DateKey.
>
> Ported.
thanks.
>
> > 3) added save(String) and save(DBConnection) methods to Persistent
> > interface so that it is enough to cast an object to Persistent to use
> > those methods.
>
> Ported. Torque-generated OMs implment these methods.
thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
