Re: Reverse Engr into erwin - Mailing list pgsql-general

I don't know about ErWin. If you look for alternatives that would=20
include a tool change=2C then continue reading.
I do use DBWrench=2C is working fairly well.

Pr=F3s:
- Multiple diagrams for same database/schema (can reduce the amount of=20
tables you are looing)=2C with some glyphs to help organize them
- True reverse and forward engineering (work most of time)
- Smart rename/recreate with data move when alter is not an option
- Support triggers=2C tables=2C schemas=2C functions=2C indexes=2C unique=20
constraints=2C primary and foreign keys
- Intuitive interface
- Capable of conversion between 4 databases supported (PostgreSQL=2C=20
Oracle=2C MS SQL Server=2C and Access)
- Use can tweak data types
- Latest release (that I don't own) support PostgreSQL arrays and other=20
special data types
- Written in Java=2C runs everywhere (I do run in Windows and Linux)
- Diagrams saved in XML format=2C it is easy to implement versioning

Cons:
- No check constraints support
- No index operator class
- Bugs in function/procedure reverse engineering/forward enginnering
- Support is so-so=2C no big deal since the tool work most of time
- Oriented to upgrades (need to buy new version to get some fixes for=20
known bugs)

You can get 30 day trial (at least=2C it was available at time I was=20
evaluating for buy).

PS: I don't work for the company that sell. I'm just a (almost happy)=20
customer that feels if they have more huge user base=2C they would add=20
more features quicker.


Regards=2C

Edson


Em 04/02/2013 20:35=2C Little=2C Douglas escreveu:
>
> Thanks in advance for thinking about my problem.
>
> As I suspect you know=2C  CA Erwin doesn't support Postgres or greenplum.
>
> But they do support ODBC for reverse engineering.
>
> When I reverse=2C Erwin executes the standard ODBC metadata queries for=20
> the system catalog.
>
> The process works fine=2C but I'm finding that the datatype that's=20
> returned is the internal PG type instead of the standard set of ANSI=20
> types.
>
> Eg=2C   a BIGINT column returns as INT8.
>
> I could live with the non-standard lables=2C if the resulting DDL would=20
> execute.  But PGadmin doesn't know the data types.
>
> I've traced the same function to PGadmin and find that it is=20
> submitting a query with the format_type(type oid) function to convert=20
> to ANSI types.
>
> I've installed the newest PG ODBC driver and the problem remains.
>
> I'm hoping that there is a setting in ODBC that I can use to have the=20
> ANSI datatypes returned.
>
> Short of that=2C  Is there anyway to change the Query that's submitted
>
> It's querying the pg_attribute=2C pg_type type with the schema name=20
> specified Pg_catalog=2C  so I don't think I can over ride the select.=20
> Perhaps a rule might work.
>
> Any suggestions on moving forward?
>
> Thanks
>
> *Doug Little*
>
> **
>
> Sr. Data Warehouse Architect | Business Intelligence Architecture |=20
> Orbitz Worldwide
>
> 500 W. Madison=2C Suite 1000  Chicago IL 60661| Office 312.260.2588 |=20
> Fax 312.894.5164 | Cell 847-997-5741
>
> *Douglas.Little@orbitz.com* <mailto:Douglas.Little@orbitz.com>*__*
>
> cid:image001.jpg@01CABEC8.D4980670 orbitz.com <http://www.orbitz.com/>=20
> | ebookers.com <http://www.ebookers.com/> | hotelclub.com=20
> <http://www.hotelclub.com/> | cheaptickets.com=20
> <http://www.cheaptickets.com/> | ratestogo.com=20
> <http://www.ratestogo.com/>| asiahotels.com <http://www.asiahotels.com/>
>