-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I think it might actually just boil down to permissions. Whilst logged in as the bioseqdbmart user can you do a select against any table in the public schema? If not, then there lies the problem.
(Certainly in Oracle permissions need to be granted on the source schema to allow the target schema owner to access it - not sure how this works in Postgres with the public schema.) cheers, Richard Brian Osborne wrote: > Richard, > > I certainly did not set out with Biomart with the idea of learning more > about Postgres but that seems to be what's happening. That's life. > > I've added a few lines to Biosql's Postgres script that allows you to create > Biosql in a specified schema, and I've modified that load_taxonomy.pl script > to load using a given database and schema. This all seems to work. Last > step, modify bioperl-db's load_seqdatabase.pl script to do the same... > > BIO > > > On 5/25/07 6:08 AM, "Richard Holland" <[EMAIL PROTECTED]> wrote: > >> Let me know how you get on with trying to do this within a non-public >> schema. > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGVuGc4C5LeMEKA/QRAt4BAJwLrr59quFd4A4YuvbW5yiHxOociQCdF884 t5mYUi29m6BT8IQAtMm2Q90= =CVSO -----END PGP SIGNATURE-----
