|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
Hi Patrick,
thanks for reporting this. I agree it's fishy and we'll need a way to improve on this but I wouldn't consider it a priority as operations such as exportTableDefinitions don't make any sense for OGM, hence we should provide a better error message but it is still a user error to attempt using such a service: OGM should never use a JDBC connection.
I'm wondering why you got that error; are you sure that is the set of configuration properties you're running with? I would expect to see it only when explicitly requesting a table creation/update.