Re: Abator: column override (@ in column names in MSSQL Server DB)

2006-11-08 Thread Mark Cooke
edback. > > I think it's a good idea to put it in the context > and then enable/disable by > table and possibly column. > > Jeff Butler > > > On 11/2/06, Mark Cooke <[EMAIL PROTECTED]> > wrote: > > > > I was sure you'd be aware of that -

Re: Abator: column override (@ in column names in MSSQL Server DB)

2006-11-02 Thread Mark Cooke
entifierDelimiters="[]"/> > > This would deal with the case where there are > strange characters in the > table name too. In the generated SQL, EVERY > identifier would be delimited. > > Jeff Butler > > > On 11/1/06, Mark Cooke <[EMAIL PROTECTED]&g

Re: Abator: column override (@ in column names in MSSQL Server DB)

2006-11-01 Thread Mark Cooke
or. I'll > work on something. > > Jeff Butler > > > > On 10/31/06, Mark Cooke <[EMAIL PROTECTED]> > wrote: > > > > Hi, > > I've tried using abator against a MSSQL server, > where > > some of the tables' column names begin with a

Abator: column override (@ in column names in MSSQL Server DB)

2006-10-31 Thread Mark Cooke
Hi, I've tried using abator against a MSSQL server, where some of the tables' column names begin with a @. I've put a column override for each of the columns to force the java property name (i.e. drop the @), which works fine. The problem comes with the generated SQL...the bad column names are int