On Tue, 9 Oct 2007, L wrote:
mysqlku.pas(16,18) Error: Identifier not found TMYSQL
mysqlku.pas(16,18) Error: Error in type definition
mysqlku.pas(18,22) Error: Identifier not found TMYSQL_ROW
mysqlku.pas(18,22) Error: Error in type definition
mysqlku.pas(74,17) Error: Operator is not
You cannot. Mysql is a pain to maintain. They break interface compatibility
almost every release.
So its mean that mysql is difficult to followed?
if yes, is there any other way to access mysql like odbc maybe?
-
Be a better Globetrotter. Get better
On Mon, 8 Oct 2007, Andi Purwito wrote:
You cannot. Mysql is a pain to maintain. They break interface compatibility
almost every release.
So its mean that mysql is difficult to followed?
Yes. The best is to stick to 1 version of MySQL as long as possible.
if yes, is there any other way
Op maandag 08-10-2007 om 22:16 uur [tijdzone -0700], schreef Andi
Purwito:
You cannot. Mysql is a pain to maintain. They break interface compatibility
almost every release.
So its mean that mysql is difficult to followed?
Yes. (It's not for nothing that ppl still use mysql 4.0 and 4.1)
Also,
mysqlku.pas(16,18) Error: Identifier not found TMYSQL
mysqlku.pas(16,18) Error: Error in type definition
mysqlku.pas(18,22) Error: Identifier not found TMYSQL_ROW
mysqlku.pas(18,22) Error: Error in type definition
mysqlku.pas(74,17) Error: Operator is not overloaded
mysqlku.pas(76,32)
On Mon, 8 Oct 2007, Andi Purwito wrote:
Hi all. This is my test program to track interface changes in mysql lib.
-
Compiling MySQLku.pas
mysqlku.pas(16,18) Error: Identifier not found TMYSQL
mysqlku.pas(16,18) Error: