Yup, it works fine. I guess this was fixed by fixing
StringUtils.chop(), right?
Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
> -----Original Message-----
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, January 04, 2001 5:26 PM
> To: Turbine
> Subject: Re: Commas in torque-generated MySQL scripts
>
>
>
> This has been fixed, tested, and it works fine.
>
> jvz.
>
> On Thu, 4 Jan 2001, Diethelm Guallar, Gonzalo wrote:
>
> > Some time ago, I reported that torque creates MySQL scripts
> > that look like
> >
> > CREATE TABLE PERSON
> > (
> > CODE INTEGER NOT NULL,
> > LAST VARCHAR (50) NOT NULL,
> > FIRST VARCHAR (50),
> > BIRTH DATE,
> > DEATH DATE,
> > PRIMARY KEY(CODE),
> > UNIQUE (LAST, FIRST),
> > );
> >
> > Notice the comma on the last line; MySQL doesn't like it.
> > It seems as if there was an attempt to fix this by adding
> > calls to chop() and checking whether the table would have
> > primary keys, unique keys, etc., but this didn't work
> > very well for WinNT (I guess chop() has problems with
> > CR vs CRLF). Sooo, I patched the templates, and things look
> > much simpler now on the VM files. The only thing is,
> > the output generated looks like this:
> >
> > CREATE TABLE PERSON
> > (
> > CODE INTEGER NOT NULL
> > , LAST VARCHAR (50) NOT NULL
> > , FIRST VARCHAR (50)
> > , BIRTH DATE
> > , DEATH DATE
> >
> > , PRIMARY KEY(CODE)
> >
> >
> > , UNIQUE (LAST, FIRST)
> >
> >
> > );
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
