I just noticed that change in the schema (date field in weblogentry) too and it breaks DB2 since the field type is not supported. I checked documentation and datetime is also not supported on Derby either. Anyways, I don't know the differences between datetime and timestamp. Why does pubtime need to be a datetime as opposed to a timestamp? Is this something that can be done via a customizable datatype as in TEXT? Just a thought.
Elias On 10/16/05, Dave Johnson <[EMAIL PROTECTED]> wrote: > > Here's my theory. We changed the weblog entry pubtime into a date field > rather than a timestamp and I bet we didn't test against PostgreSQL (I > know I didn't). > > According to the docs below, we need to do the temp table trick if we > want to change a column type in PostgreSQL: > > http://techdocs.postgresql.org/techdocs/updatingcolumns.php > > Then, we may have data type issues. I hope PostgreSQL has a compatible > DATETIME field. > > I'm out of the office for the next couple of days, so I won't have a > chance to look into this. > > - Dave > > > On Oct 16, 2005, at 12:19 AM, Henri Yandell wrote: > > > On 10/12/05, Dave Johnson <[EMAIL PROTECTED]> wrote: > >> Is this complete? Can we close the JIRA issues for DB2 and Derby > >> support and if not, what remains to be done? > >> > >> And BTW, the 2.0 bug list is getting pretty slim. > > > > Heh, there I was thinking it had a long time to go; which explained > > the problems I was seeing where posting an entry to a new blog > > buggered it up big time. > > > > http://opensource2.atlassian.com/projects/roller/browse/ROL-844 > > > > >
