Announcement

Collapse
No announcement yet.

table name KEYS conflicts with mysql keyword

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • table name KEYS conflicts with mysql keyword

    Hi,

    I was trying to setup mirth with mysql starting with the data definitions. mysql 5.0 did not like the table name KEYS, and so i added the database qualifier mirth.KEYS to create the table. i am getting an exception though in ConfigurationController class (i should have seen this coming) everytime table KEYS is selected because the code does not contain the qualifier. other than modifying the code, is there an easier way to resolve this conflict, say a switch in mysql?

    thanks a bunch!

    Erwin Pader
    Health Management Associates, Inc.
    Naples, FL

  • #2
    Re: table name KEYS conflicts with mysql keyword

    Are you looking at replacing the internal Mirth Hypersonic DB with MySQL?
    Chris Lang

    Comment


    • #3
      Re: table name KEYS conflicts with mysql keyword

      Chris,

      yes i am. btw, i had to comment out the closing of the db connection in Connection class for resultset to work. it blew up on me (resultset closed exception) when it was attempting to read the encrypted key. sounds like hypersonic's driver does not care if conn is closed before a getting the resultset.

      a few more things:

      LONGVAR does not work with MySQL so i used varchar.
      DDL for generated sequence id syntax is different in MySQL
      one of the tables had a varchar key length of 4000 which MySQL did not like. had to trim it down to 1000



      Comment


      • #4
        Re: table name KEYS conflicts with mysql keyword

        On a related note, I'm looking at replacing HSQLDB with PostgreSQL for several reasons. Haven't tried anything yet, but am interested... Any suggested reading material?

        mike

        Comment

        Working...
        X