Acho que sou obrigado a comentar... pois o MYSQL tem tudo isto:
Stored procedures and triggers
- Stored procedures allow you to create functions and subroutines that
run on the server. This makes it possible to grant access to specific
queries without granting carte blance access to the underlying data, or
validate data in the database before it is stored. Triggers can be
configured to fire when certain conditions are fulfilled.
- The MySQL database server will provide hooks for implementing stored procedures in multiple languages, as well as including support for the Persistent Stored Modules syntax defined as part of ANSI SQL-99.
- Views allow you to configure alternative views of existing tables
without changing the underlying table structure. They can be used to
grant limited access to tables, or make it easier to construct certain
types of queries.
- Using the InnoDB or Berkeley DB (BDB) storage engines, the MySQL
database server supports transactions. The InnoDB storage engine also
supports foreign key constraints.
[]'s!
At 14:50 12/2/2003 -0300, you wrote:
O problema esta nas diferencas entre os banco de dados. O Mysql nao eh um
banco de dados relacional, nao tem 'constraints', Triggers, integridade
referencial, etc.... Desta forma, se no DB2 voce utiliza estas ferramentas,
com certeza o trabalho serah bem dificil.
Jah o postgresql eh relacional e apresenta funcoes similares ao db2. Ao meu
ver, o PostgreSQL deverah ser sua opcao.
