apache.org
Subject: RE: DbMerger/MySQL compatibility
In DbLoader.java, circa line 380, there is a reference to the NULLABLE
field. In the ResultSet I'm looking at, there's no such field - there is
however an IS_NULLABLE field.
-Original Message-
From: Tore Halset [mailto:[EM
M
To: user@cayenne.apache.org
Subject: Re: DbMerger/MySQL compatibility
On Aug 28, 2008, at 21:03, Scott Anderson wrote:
>> Is it possible to detect this via jdbc?
>
> A rather long-winded way to detect table type is:
> SHOW CREATE TABLE [table name];
>
> This will return th
Woops, hit send too soon on the last email
> Can you try with the latest build?
> http://hudson.zones.apache.org/hudson/job/Cayenne-
> trunk/lastBuild/org.apache.cayenne$cayenne-modeler-java/
Nope; it's not fixed in the latest nightly. Additionally, the same
problem we discussed the other day in
> Can you try with the latest build?
> http://hudson.zones.apache.org/hudson/job/Cayenne-
> trunk/lastBuild/org.apache.cayenne$cayenne-modeler-java/
Nope; it's not fixed in the latest nightly. Additionally, the same
problem we discussed the other day in regards to Derby is occurring:
ALTER TABLE m
Not sure if that's helpful at all, but we have a mechanism to detect
the default table type on a given DB. See MySQLSniffer for details
("SHOW VARIABLES LIKE 'table_type'"). Maybe not that helpful, as (1)
it is not using metadata, but rather a MySQL specific command and (2)
DB default doesn
On Aug 28, 2008, at 21:03, Scott Anderson wrote:
Is it possible to detect this via jdbc?
A rather long-winded way to detect table type is:
SHOW CREATE TABLE [table name];
This will return the full CREATE TABLE instruction required to rebuild
that table. If this is already how you determine w
ilto:[EMAIL PROTECTED]
Sent: Thursday, August 28, 2008 2:07 PM
To: user@cayenne.apache.org
Subject: Re: DbMerger/MySQL compatibility
On Aug 28, 2008, at 19:34, Scott Anderson wrote:
> It looks like the DbMerger in 3.0M4 isn't properly detecting whether
> NULL is allowed for columns when
On Aug 28, 2008, at 19:34, Scott Anderson wrote:
It looks like the DbMerger in 3.0M4 isn't properly detecting whether
NULL is allowed for columns when using MySQL. Is this another issue
that
has already been fixed in trunk?
I do not remember. Can you try with the latest build?
http://hudson
It looks like the DbMerger in 3.0M4 isn't properly detecting whether
NULL is allowed for columns when using MySQL. Is this another issue that
has already been fixed in trunk?
Does it seem reasonable to expect the MySQL adapter to know that MyISAM
doesn't support db-enforced FKs? I don't have the a
