Subject | isql issue with FB 2.1 on Mac OS X 10.4.11 PPC |
---|---|
Author | Thomas Woinke |
Post date | 2008-04-21T17:59:02Z |
Hi all,
I am having some issues after having installed the SuperServer-Package
of Firebird 2.1 for Mac OS PPC.
I get no results when issuing any query in isql. Issuing the query
again results in the error message
-SQL error code = -519
-The prepare statement identifies a prepare statement with an open cursor
Here's what to do to reproduce the error, at least on my system:
Marvin:~ thomas$ isql -u sysdba -p masterkey
Use CONNECT or CREATE DATABASE to specify a database
SQL> create database 'test.fdb';
SQL> connect 'test.fdb';
Commit current transaction (y/n)?y
Committing.
Database: 'test.fdb', User: sysdba
SQL> select * from rdb$database;
SQL> select * from rdb$database;
Statement failed, SQLCODE = -519
Dynamic SQL Error
-SQL error code = -519
-The prepare statement identifies a prepare statement with an open cursor
SQL>
Connecting from PHP 5.2.6RC6 (freshly compiled against FB2.1) works flawlessly.
I then tried CS just to be sure. The above error does not occur, but
isql keeps segfaulting on exit.
Any ideas?
Regards,
Thomas
I am having some issues after having installed the SuperServer-Package
of Firebird 2.1 for Mac OS PPC.
I get no results when issuing any query in isql. Issuing the query
again results in the error message
-SQL error code = -519
-The prepare statement identifies a prepare statement with an open cursor
Here's what to do to reproduce the error, at least on my system:
Marvin:~ thomas$ isql -u sysdba -p masterkey
Use CONNECT or CREATE DATABASE to specify a database
SQL> create database 'test.fdb';
SQL> connect 'test.fdb';
Commit current transaction (y/n)?y
Committing.
Database: 'test.fdb', User: sysdba
SQL> select * from rdb$database;
SQL> select * from rdb$database;
Statement failed, SQLCODE = -519
Dynamic SQL Error
-SQL error code = -519
-The prepare statement identifies a prepare statement with an open cursor
SQL>
Connecting from PHP 5.2.6RC6 (freshly compiled against FB2.1) works flawlessly.
I then tried CS just to be sure. The above error does not occur, but
isql keeps segfaulting on exit.
Any ideas?
Regards,
Thomas