ErWin 7.2 does not provide support for PostgreSQL, indeed with few tricks it still can be used to model database and generate valid SQL code.
(Note: In ErWin 7.3 templates look very different from 7.2, but nevertheless, I believe, similar approach still can be applied).
Trick 1. Use Oracle 10.x as the target DBMS
PostgreSQL has common ideology with Oracle and, in my opinion, is the best choice for PostgreSQL needs.
Trick 2. Fix syntax differences
I have encoundered two syntax differences – in the order designator in the column specifier of CREATE INDEX statement and extra parenthesis in ALTER TABLE ADD CONSTRAINT
Following samples illustrate what causes PostgreSQL to fail with generated code:
CREATE INDEX Publisher_xIF1 ON Publisher (PublisherID ASC);
ALTER TABLE Publisher
ADD (CONSTRAINT Publisher_fObject FOREIGN KEY (ObjectID) REFERENCES Object(ObjectID) ON DELETE CASCADE);
This can be fixed by altering ErWin FE template as the following:
2.1. Copy and rename Oracle.erwin_fe_template to Postgre.erwin_fe_template and then open it in a text editor.
|
2.2. Find 2.3. Below that find and remove line containing |
 |
|
2.4. Find 2.5. Remove 2.6. Switch you project to use this template These two tricks are essential to produce valid SQL code from an ErWin model that contain no Oracle specific features, like table partitions, logging, validation, etc. If you already have an Oracle model which you prefer to keep intact and still be able to generate SQL for Postgress, you will need to void all parts of FE template responsible for Oracle specific features. |
 |
|
Trick 3. Implement use of 3.1. Find first occurrence of |
|
|
3.2. Add
|
 |
|
3.3. At the end of the file add |
|
SPItemBegin = Extra Properties
10000:
{#
ForEachVectorReferenceX("Child Relations Ref")
{
[ IsPropertyEqual("Type","9")
" INHERITS("
[
PushReferenceX("Parent Entity Ref")
[ [OwnerX"."]PhysicalNameX ]
PopX
]
")"
]
}
#}
SPItemEnd
|
 |
Post a Comment