Hi!
I understand that solutión, the problem is that it doesn't work
anymore. I was working with mysql client days ago without troubles, but
now it's impossible. We did 2 things before:
Upgrade from MySQL 4.1 to 5.0.22
Upgrade from Sequoia 2.10.3 to 2.10.4 (released last week).
With this deployment it was working a few days, but now it's impossible
to execute any query without receive this error. I check also that
sequoia using JDBC is working without troubles. I reinstall
carob/libmysequoia again in this machines and in others without lucky.
It could be some kind of bug with this versions of MySQL or Sequoia
latest stable release?
> El mié, 24-01-2007 a las 11:28 +0200, Csaba Simon escribió:
> > Hi Raúl,
> >
> > The problem is that until you are not connected to the cluster you can't
> > issue any query. This is why you get the "command out of sync" error
> > message. You are connected to the cluster only if you specify the
> > username, password, hosts and database name for mysql_real_connect(). If
> > you not specify the database than libMySequoia will do a "lazy" connect.
> > This means that will return OK when you specify only the username,
> > password and host BUT will not do a real connection to the cluster until
> > you not specify the database name.
> >
> > Let see your user scenarios:
> > 1. for PHP if you modify the mysqli_query($this->Link_ID, "USE
> > $Database") to mysql_select_db($this->Link_ID, "$Database") the
> > application will work.
> > 2. for mysql command line client you can use the following trick:
> > in the /etc/mysequoia/mysequoia.conf specify this line:
> > database=VirtualDatabase
> >
> > Regards,
> > Csaba
> >
_______________________________________________
Carob mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/carob
