Developers : Accessing the Database from a Plugin : Comments

RE: Accessing the Database from a Plugin

sebastien@veodia.com — Fri, 19 Dec 2008 19:05:59 GMT

This tutorial is missing one point : the plugin.xml file must contain:

<databaseKey>feedblog</databaseKey>
<databaseVersion>1</databaseVersion>

where databaseKey is the schema name used in schema.xml, in order to tell clearspace to create the tables.

RE: Accessing the Database from a Plugin

communities@jivesoftware.com — Fri, 19 Dec 2008 19:07:29 GMT

Hi Sebastien,

Thanks for that. I remember that had me hung up for a while as well. I will add that to the doc. Thanks

RE: Accessing the Database from a Plugin

communities@jivesoftware.com — Tue, 17 Mar 2009 15:05:30 GMT

Can you describe this code of FeedBlogDAOImpl calss:

long id = nextID(impl);

Where I can find this nextID method sources?

What is the solution for generating primary keys?

RE: Accessing the Database from a Plugin

communities@jivesoftware.com — Sun, 16 Aug 2009 04:47:32 GMT

I cant believe I am posting this, but I just spent an hour stepping through code to figure this one out...so I thought I would mention it just so it is some where. When using Postgres, in your plugin.xml, you should not have any "spaces" in your "databaseKey". My rule of thumb is always to avoid spaces, but as I was flying through the plugin.xml setup..I accidentally put a space instead of a dash. This caused all sorts of nasty stuff to happen...specifically a random error that said...syntax error after the "," in your SQL statement...all my tables in schema.xml were created....but it was the insert into the jiveVersion table that was barfing.

Avoid spaces in the database key, and live a happy life...Hope this helps someone =)

Updated:

In fact, this may not have had anything to do with the problem. I tried a purge with a new configuration for my plugin, and got the same error. What had worked, was a manual insertion of my plugin into jiveVersion, to bypass the problem. Will look into this a bit more when I get a chance to loop back to it. Something's a bit odd here. Using 3.0.6 and Postgres (eval.exe) release.