Menu

#51 Fully-qualified names schema.table not working

open
nobody
None
2
2009-02-17
2007-03-28
No

- I am generating for Postgres 8.2.
- My tables are distributed over several schemas.
- One table name happens to have the same name as a table in Postgres' administrative schema pg_catalog

I am unable to generate classes for *my* table xyz.parameters, but I always get pg_catalog.parameters.

I tried "mgrwriter.include=xyz.parameters" - no table generated whatsoever.
I tried "jdbc.schema=xyz" - wrong table from pg_catalog is generated *with* compilation faults.

Hartmut

Discussion

  • Gerits Daan

    Gerits Daan - 2007-04-27

    Logged In: YES
    user_id=913855
    Originator: NO

    Hello hartmut,

    I know this is a problem, because Sql2Java generates all it's code into one big happy directory. This is known to us and will be fixed in the next release. If i find some time, i'll try to figure out how to change this so you'll have it sooner.

    Daan Gerits

     
  • Alain Fagot Béarez

    Logged In: YES
    user_id=4796
    Originator: NO

    While looking throughout the code for some other stuff, I may have found a way to help you specify the tables you want. By specifying the schema in the tablenamepattern property of the sql2java.properties configuration file as in:

    tablenamepattern=xyz.parameters, otherSchema.patt%, %pattern

    To tell the truth, I find the way to tell what to include and what to exclude somehow confusing. I hope the next 3.0 version will solve many of these issues.

     
  • Alain Fagot Béarez

    • priority: 5 --> 2
     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.