Thread: PostGres and ERwin

Hiya,

If its any help, I've tried this and didn't have much luck with the ODBC
options -  also had problems with getting to to put NOT NULL constraints on
tables too.  Didn't seem to make a difference with ODBC 2.0 or 3.0.  What I
ended up doing was picking "Interbase" as my target server, purely because
(by a process of elimination!) I could get this to generate SQL that worked
with Postgres, and then using the Forward Engineer-Generate report option
(with some of the options like create domian turned off).  This made a
script which I could then run against my Postgres database.

Tamsin




 -----Original Message-----
From: pgsql-general-owner@hub.org [mailto:pgsql-general-owner@hub.org]On
Behalf Of Carlos Felipe Zirbes
Sent: 14 August 2000 13:55
To: pgsql-general@postgresql.org
Subject: [GENERAL] PostGres and ERwin


Hi.

Has anyone ever used erwin to connect to postgres?
I have been trying to use erwin 3.5.2 sp2 to connect to pgsql via the latest
odbc driver available and can't get erwin do create PK and FK constraint
correctly. What odbc version should I use? 2.0 or 3.0?

Any help or report about this matter is welcome.

Thanks in advance,
 Zirbes

Interbase, ahn?

I'll give it a try.
Unfortunately, this strategy won't work for complete compare, the tool I use/like the best. Perhaps the only solution is to keep awaiting for erwin's next version, tough it seems something not very likely to happen in the next 10 or 15 years...  :^)

Thanks for your help,
Carlos Zirbes

> -----Original Message-----
> From: Tamsin [mailto:tg_mail@bryncadfan.co.uk]
> Sent: Terça-feira, 15 de Agosto de 2000 05:16
> To: pgsql-general@postgresql.org
> Subject: RE: [GENERAL] PostGres and ERwin
>
>
> Hiya,
>
> If its any help, I've tried this and didn't have much luck
> with the ODBC
> options -  also had problems with getting to to put NOT NULL
> constraints on
> tables too.  Didn't seem to make a difference with ODBC 2.0
> or 3.0.  What I
> ended up doing was picking "Interbase" as my target server,
> purely because
> (by a process of elimination!) I could get this to generate
> SQL that worked
> with Postgres, and then using the Forward Engineer-Generate
> report option
> (with some of the options like create domian turned off).  This made a
> script which I could then run against my Postgres database.
>
> Tamsin