I can do that. Thanks
Nathan
-Original Message-
From: Bryan Pendleton [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 09, 2007 10:52 AM
To: Derby Discussion
Subject: Re: Problem with default date values
> I tried the 10.3.1.4 release, and my test case if failing before I get
> to the
The stacktrace I am getting in my app is:
ERROR 22005: An attempt was made to get a data value of type 'long' from
a data value of type 'DATE'.
at
org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
at
org.apache.derby.iapi.types.DataType.dataTypeConversion(U
I tried the 10.3.1.4 release, and my test case if failing before I get
to the other error. It's failing on this call:
tableRS = conn.getMetaData().getTables(getCatalogName(),
getSchemaName(), null, new String[]{"TABLE", "GLOBAL TEMPORARY", "LOCAL
TEMPORARY", "ALIAS", "SYNONYM"});
with this stack
I checked, and I am running 10.2.2.0. The issue you list talks about
setting the default value for a table with rows, but my table doesn't
have any. The full list of SQL ran against the table is:
CREATE TABLE defaultValueTest (
id int,
intA int,
textA varchar(5),
I'm creating a table with the following SQL:
CREATE TABLE defaultValueTest (
id int,
intA int,
textA varchar(5),
booleanA SMALLINT,
dateA DATE,
timeA TIME,
datetimeA TIMESTAMP
)
Then running the SQL:
ALTER TABLE defaultValueTest ALTER COLUMN dateA WITH DEFAULT
DATE('2007-
Hi, I just wanted to point out that the latest release of LiquiBase now
supports Derby. LiquiBase is a java-based LGPL tool for creating,
managing, and applying database changes/refactorings.
It is similar in its goals to Rails' ActiveMigration, but works well
with multiple authors and/or br
