From: Elisabetta M. <man...@pc...> - 2008-12-16 01:16:36
|
Hi Isabelle, you don't need to check in svn to test private plugins. You modify your plugin in your $PROJECT_HOME and build $GUS_HOME. To test the plugin you can run it in non-commit mode. If you want to test and commit, by appropriately changing the Revision number of the plugin in $GUS_HOME you should be able to hack it to think that it has been checked in. Elisabetta On Mon, 15 Dec 2008, Isabelle Phan wrote: > How do I test private (ie my own) plugins? > > I cannot load GO terms because the table definition for the temporary > load table is broken for Postgres. > > I updated the InsertGeneOntology plugin, but I don't want to check it > into subversion, because it will break for the default Oracle > implementation. > > At the moment I am competely stuck, and appreciate any help, > > Thanks > > Isabelle > >> I rejoiced too soon.... >> >> There is a problem with the GO plugin, after the GO terms have been >> loaded, I am getting: >> >> Transitive closure (length 4000418): added 0 edges >> DBD::Pg::st execute failed: ERROR: prepared statement "dbdpg_2" does >> not exist |