On Tue, 10 Mar 2009, Moritz Onken wrote:
SQL::Translator::Producer:: SQLServer doesn't seem to honour quote_char and
SQL::Translator::Producer:: friends.
No, doesnt look like it does. Patches welcome ;)
That's not related to fREW's problem though.
Jess
Am 09.03.2009 um 23:24 schrieb fREW Schmidt:
Hi all!
We are dealing with some weird issues because our database has silly
column names. Specifically speaking we have a column called
'user'. user is a reserved word in T-SQL (we are using SQL
Server.) Anyway, this is the error we get:
On Mon, Mar 9, 2009 at 5:24 PM, fREW Schmidt wrote:
> Hi all!
>>>
>>> We are dealing with some weird issues because our database has silly
>>> column names. Specifically speaking we have a column called 'user'. user
>>> is a reserved word in T-SQL (we are using SQL Server.) Anyway, this is the
>
> Hi all!
>>
>> We are dealing with some weird issues because our database has silly
>> column names. Specifically speaking we have a column called 'user'. user
>> is a reserved word in T-SQL (we are using SQL Server.) Anyway, this is the
>> error we get:
>>
>> DBIx::Class::ResultSet::find():
Am 09.03.2009 um 20:06 schrieb fREW Schmidt:
Hi all!
We are dealing with some weird issues because our database has silly
column names. Specifically speaking we have a column called
'user'. user is a reserved word in T-SQL (we are using SQL
Server.) Anyway, this is the error we get:
fREW Schmidt wrote:
Hi all!
We are dealing with some weird issues because our database has silly
column names. Specifically speaking we have a column called 'user'.
user is a reserved word in T-SQL (we are using SQL Server.) Anyway,
this is the error we get:
DBIx::Class::ResultSet::f
Hi all!
We are dealing with some weird issues because our database has silly column
names. Specifically speaking we have a column called 'user'. user is a
reserved word in T-SQL (we are using SQL Server.) Anyway, this is the error
we get:
DBIx::Class::ResultSet::find(): Error executing 'SELECT
