AW: Non Standard Names // Fixed

From: Korbinian Bachl (korbinia..hiskyworld.de)
Date: Fri Jan 13 2006 - 11:08:13 EST

  • Next message: Dirk Lattermann: "how to select instances with empty to-many relation"

    BUG FOUND !!!

    Hi Andrus,

    i found the "bug" - in fact, it was a mistake by me combined with a bug in
    Postgres - i created the DB with:

    CREATE DATABASE wwtest
      WITH OWNER = tuser
           ENCODING = 'SQL_ASCII'
           TABLESPACE = pg_default;

    in PG Admin - if PG would care more it wouldnt accept a tabe called "länder"
    etc. in a SQL_ASCII environment...
    after making a new one:

    CREATE DATABASE wwtest2
      WITH OWNER = tuser
           ENCODING = 'UTF8'
           TABLESPACE = pg_default;

    everything works as expected - so, the only bug is that PG Admin as well as
    PG itself dont watch this close at their encoding type,

    Regards

    Korbinian

    >
    >
    >
    > > -----Ursprüngliche Nachricht-----
    > > Von: Andrus Adamchik [mailto:andru..bjectstyle.org]
    > > Gesendet: Freitag, 13. Januar 2006 14:50
    > > An: cayenne-use..bjectstyle.org
    > > Betreff: Re: Non Standard Names
    > >
    > > Did it happen right after reengineering or only after you saved and
    > > reopened the model?
    > >
    > > In the first case I guess the solution would lie on the PostgreSQL
    > > driver end (although this page implies that this shouldn't
    > be an issue
    > > with newer postgres - http://jdbc.postgresql.org/documentation/
    > > 81/connect.html#connection-parameters)
    > >
    > > I suspect it's the later case. If so, in the Modeler go to Tools ->
    > > Preferences -> General and select custom file encoding and then
    > > "UTF-8".
    > >
    > > Andrus
    > >
    >
    >

    This archive was generated by hypermail 2.0.0 : Fri Jan 13 2006 - 11:08:09 EST