Foreign Key on different Databases


We use the Data Modeler for different Databases.
At first, we made different models for the different databases. This is not good.

Now, we make one model (Actually we use PostgreSQL, Microsoft SQL and Interbase). For different datatypes we use domains.

All that works fine. 
But, we have to rework at the foreign keys. Rules on delete/update

The default ist NO ACTION on all databases. This works without any definition.
BUT the Data Modeler make RESTRICT for PostgreSQL instead of NO ACTION or instead of nothing. This don't work on MS-SQL.
Either you make nothing for Foreign Key with No Action or you make the keyword "NO ACTION".

Is this possible?
What do you mean by "don't work on MS-SQL"?
Do I understand you are using the same SQL script generated from the same Data Modeler project, for both SQL Server and PostgreSQL?

Yes, we want to use the same script. 
initially we had different scripts, but the maintenance was very cumbersome.
Now, we use one script for each database-system for creating the domains. And one script for the whole database on all server.



ALTER TABLE the_table_name ADD CONSTRAINT foreign_key_constraintname
  FOREIGN KEY (id)
  REFERENCES other_table (other_id)
POSTGRESQL==>
  ON DELETE RESTRICT
  ON UPDATE RESTRICT;
MSSQLSQL==>

  ON DELETE NO ACTION
  ON UPDATE NO ACTION;


BUT, the RESTRICT or NO ACTION is the default value for all database we know.
The simplest way is, don't create the last two lines, if no action is desired.

This has been improved internally. Next Data Modeler release will have both "No action" and "Restrict" options, and Postgres and SQLite (the only two supported databases that differentiate both options) will behave accordingly.

Fine, thank you all.