Yeah - different databases have different delimiters. DB2 uses double quotes. So it will have to be configurable.
Right now I'm considering adding an option like this:
<table tableName="some table" identifierDelimiters="[]"/>
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]> wrote:
Jeff,
Great, that's brilliant!
However...I just realised I was wrong about the
required delimiters - the column should be enclosed in
[] in the queries, not " or '...
Mark.
--- Jeff Butler <[EMAIL PROTECTED]> wrote:
> There's no solution for this now in Abator. 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 @.
> > 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 interpreted as
> > variables (that's what MSSQL's error says it
> thinks it
> > is).
> > For MSSQL - The column name should be delimited
> with
> > either a single or double quote (I Think).
> >
> > I don't suppose there are any undocumented options
> on
> > the column or SQL generator elements with which I
> can
> > force the column names to be delimited in the SQL?
> >
> > Thanks in Advance,
> > Mark.
> >
> > Send instant messages to your online friends
> http://uk.messenger.yahoo.com
> >
>
Send instant messages to your online friends http://uk.messenger.yahoo.com
