Several changes are needed in the Openfire database schema.
Openfire DB schema uses certain field names which can conflict with reserved keywords of some SQL servers (e.g. Sybase SQL Anywhere, Firebird SQL), conflicting names and possible replacements are:
password - xmppPassword (in tables jiveUser, mucRoom ) value - privvalue ( jivePrivate ) value - vcard ( jiveVCard ) message - xmppmessage ( jiveOffline ) domain - xmppdomain ( jiveRemoteServerConf ) time - logtime ( mucConversationLog )
Environment
None
Activity
Show:
Sabine Dinis Blochberger August 9, 2007 at 6:53 PM
Like in PHP, you could add an option for quoting sybase-style ("magicquotes") perhaps.
dna May 18, 2007 at 2:54 AM
Renaming is not required, just quote the tables and fieldnames correct.
for example: MSSQL: [myTable] or [passwordField] PostgreSQL: "myTable" or "passwordField" MySQL: `myTable` or `passwordField`
The nex problem is that you're using case sensitive table and fieldnames. PostgreSQL for example processed the table jiveUser without quotes as jiveuser. If you use in antoher place "jiveUser" (with quotes) you get the exception that the relation "jiveUser" does not exist because it is "jiveuser".
Several changes are needed in the Openfire database schema.
Openfire DB schema uses certain field names which can conflict with reserved keywords of some SQL servers (e.g. Sybase SQL Anywhere, Firebird SQL), conflicting names and possible replacements are:
password - xmppPassword (in tables jiveUser, mucRoom )
value - privvalue ( jivePrivate )
value - vcard ( jiveVCard )
message - xmppmessage ( jiveOffline )
domain - xmppdomain ( jiveRemoteServerConf )
time - logtime ( mucConversationLog )