Subject | Re: [IBO] Problem executing script with dialect 1 |
---|---|
Author | Thomas Steinmaurer |
Post date | 2008-09-24T14:59:02Z |
Hi!
c:\Programme\Firebird\Firebird_210_3050\bin>isql -i g:\script.sql
Use CONNECT or CREATE DATABASE to specify a database
SQL warning code = 301
-DATE data type is now called TIMESTAMP
I explicitly set the sql dialect to 1 in the script, so why isn't the
DATE data type allowed? Weird.
--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/
>> I get the following error message:No.
>> ISC ERROR CODE:335544569
>
>
>
> This error returned from server after IBO send statement to server and
> try execute it. It`s not IBO error.
>
> Standard ISQL.EXE or IBExpert perform script without errors?
c:\Programme\Firebird\Firebird_210_3050\bin>isql -i g:\script.sql
Use CONNECT or CREATE DATABASE to specify a database
SQL warning code = 301
-DATE data type is now called TIMESTAMP
I explicitly set the sql dialect to 1 in the script, so why isn't the
DATE data type allowed? Weird.
--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com
My blog:
http://blog.upscene.com/thomas/