linux-traipu team mailing list archive

[Tim Plessers <tim.plessers@xxxxxxxxxxxx>]

Public bug reported:

Hello,

I'm using the drizzle-jdbc driver to interface with MySQL. Everything
works well on MySQL 5.1.x, but on 5.0.x I receive an error :

2013-02-12 16:36:03,234 INFO [STDOUT] Feb 12, 2013 4:36:03 PM org.drizzle.jdbc.internal.mysql.MySQLProtocol executeQuery
WARNING: Could not execute query org.drizzle.jdbc.internal.common.query.DrizzleQuery@67adf2d7: Unknown table 'referential_constraints' in information_schema
2013-02-12 16:36:03,243 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1109, SQLState: 42S02
2013-02-12 16:36:03,244 ERROR [org.hibernate.util.JDBCExceptionReporter] Unknown table 'referential_constraints' in information_schema

information_schema.referential_constraints is indeed available from
MySQL 5.1.x on. I did some Googling on this issue, but I can't seem to
find a solution for it. Is upgrading to 5.1.x the only possibility, or
can this be fixed somehow?

Kind Regards.
Tim.

** Affects: drizzle
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/1129164

Title:
  Unknown table 'referential_constraints' in MySQL 5.0.x

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  New

Bug description:
  Hello,

  I'm using the drizzle-jdbc driver to interface with MySQL. Everything
  works well on MySQL 5.1.x, but on 5.0.x I receive an error :

  2013-02-12 16:36:03,234 INFO [STDOUT] Feb 12, 2013 4:36:03 PM org.drizzle.jdbc.internal.mysql.MySQLProtocol executeQuery
  WARNING: Could not execute query org.drizzle.jdbc.internal.common.query.DrizzleQuery@67adf2d7: Unknown table 'referential_constraints' in information_schema
  2013-02-12 16:36:03,243 WARN [org.hibernate.util.JDBCExceptionReporter] SQL Error: 1109, SQLState: 42S02
  2013-02-12 16:36:03,244 ERROR [org.hibernate.util.JDBCExceptionReporter] Unknown table 'referential_constraints' in information_schema

  information_schema.referential_constraints is indeed available from
  MySQL 5.1.x on. I did some Googling on this issue, but I can't seem to
  find a solution for it. Is upgrading to 5.1.x the only possibility, or
  can this be fixed somehow?

  Kind Regards.
  Tim.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/1129164/+subscriptions