Generating Table API in designer 2000
From: Robert Feinman <robertdfeinman_at_worldnet.att.net>
Date: Thu, 24 Jun 1999 20:33:12 -0400
Message-ID: <3772CE48.D0F15AAB_at_worldnet.att.net>
The version 2.1.x of Designer has the facility to generate a table API which gets installed as a series of packages and triggers. Some of the functionality of the API replicates standard constraints. Does anyone have any experience with using so much procedural code in a transaction database?
What is the impact on performance?
If performance is about the same as using check constraints, etc. is one better than the other?
I understand that some of the things the API can perform were not automatically available previously such as cascading updates and deletes, but
I was able to build my own packages to enforce these as needed. So the question has to do mostly with check constraints and the like.
Date: Thu, 24 Jun 1999 20:33:12 -0400
Message-ID: <3772CE48.D0F15AAB_at_worldnet.att.net>
The version 2.1.x of Designer has the facility to generate a table API which gets installed as a series of packages and triggers. Some of the functionality of the API replicates standard constraints. Does anyone have any experience with using so much procedural code in a transaction database?
What is the impact on performance?
If performance is about the same as using check constraints, etc. is one better than the other?
I understand that some of the things the API can perform were not automatically available previously such as cascading updates and deletes, but
I was able to build my own packages to enforce these as needed. So the question has to do mostly with check constraints and the like.
-- Robert Feinman, Ph.D Database Doctor robertdfeinman_at_worldnet.att.netReceived on Fri Jun 25 1999 - 02:33:12 CEST