Hi. We’ve created an OpenFire schema definition for Blackfish SQL so we can use our preferred database for our chat services on the CodeGear Developer Network and we’ve run into a minor snag.
Blackfish SQL treats “time” as a reserved word, so in order to retain that field name we’ve had to quote it. However, that means a) all queries need to quote the time field, which means lots of query changes, b) that the time field becomes case sensitive in the queries, and c) that we have to modify the OpenFire source code to support Blackfish SQL.
The other option, to avoid case sensitivity issues and quoting syntax, is to rename the time field to something else. This change still results in c) above.
I’m surprised to find that “time” has not been an issue with other SQL servers. We’d like to provide a schema for Blackfish SQL support, particularly because the liberal license we provide for deploying it could mean easy adoption for open source projects like OpenFire. Does anyone have suggestions for ways to support Blackfish SQL with OpenFire that minimize the impact or changes to the source? Has anyone else reported issues with “time” being a reserved word for their database backend?
Thanks for any advice you can offer.