On Nov 20, 2007, at 7:15 PM, Mike Schrag wrote:
I'm still getting the no space between the VARCHAR and NOT NULL in
3.3.4655 of WOLips.
This is because the regex I'm using is wrong ... I use \w (or \W ..
i don't recall) and I think it's not matching ) on varchar(xxx)
Cool... look forward t
I'm still getting the no space between the VARCHAR and NOT NULL in
3.3.4655 of WOLips.
This is because the regex I'm using is wrong ... I use \w (or \W .. i
don't recall) and I think it's not matching ) on varchar(xxx)
In addition, mysql complains that the double quotes around
CATEGORY_NAME
Since this is along the same lines, I thought I'd add to the thread...
I'm using mysql and when generating SQL for a simple entity, I get the
following:
CREATE TABLE CATEGORY ("CATEGORY_NAME" VARCHAR(255)NOT NULL,
"CATEGORY_OID" INTEGER NOT NULL, "CATEGORY_ORDER" INTEGER NOT NULL);
ALTER
Right, I remember ... I actually still have that class flying around
in my project for the stuff we were talking about the last time: SQL
generation for sub entities and not null attributes. Is that still
necessary?
Can you send me that code, actually? That should just go into the
core ...
On 18.11.2007, at 20:22, Mike Schrag wrote:
* Declare a class named
"org.objectstyle.wolips.eomodeler.EOModelProcessor"
Right, I remember ... I actually still have that class flying around
in my project for the stuff we were talking about the last time: SQL
generation for sub entities and
I'd have to take a closer look at that, but what I don't understand
from your example: if in both cases the table name is not quoted, it
should not be a problem as the conversion to lowercase happens in
both cases. I'm not using pk generation but I'm pretty sure that it
would work if either
On 18.11.2007, at 18:44, Theodore Petrosky wrote:
CREATE TEMP TABLE EOF_TMP_TABLE AS SELECT
SETVAL('maintable_seq', (SELECT MAX(theoid) FROM
maintable));
Notice the table name is not quoted so postgresq1 will
fold the name to lower case. the next line deletes the
table and fails:
DROP TABLE EO
Yes I am using Postgresql and this fixes most of the
problems... however I see that the sql creates a temp
table:
CREATE TEMP TABLE EOF_TMP_TABLE AS SELECT
SETVAL('maintable_seq', (SELECT MAX(theoid) FROM
maintable));
Notice the table name is not quoted so postgresq1 will
fold the name to lower c
On 18.11.2007, at 08:01, Theodore Petrosky wrote:
I have a little problem (looks like a bug)
I created a rather simple Entity with only two
columns.. when I press "Generate SQL" the "NOT NULL"
constraint has no space before it I don't know if
this is an old issue or a new one.
CREATE TABLE
This is WO 5.4 bug rather than an Entity Modeler bug, though I've just
now committed a workaround for it for Entity Modeler that will
reinsert spaces. It will be in the next nightly.
ms
On Nov 18, 2007, at 10:01 AM, Theodore Petrosky wrote:
I have a little problem (looks like a bug)
I cr
I have a little problem (looks like a bug)
I created a rather simple Entity with only two
columns.. when I press "Generate SQL" the "NOT NULL"
constraint has no space before it I don't know if
this is an old issue or a new one.
CREATE TABLE MainTable ("personname" textNOT NULL,
"theoid" int
11 matches
Mail list logo
