Re: ODBC was: Trigger programme without a trigger. -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

rob@xxxxxxxxx wrote:

In this one I was leaving triggers, constraints, real date fields and everything else of value out of it.

Why? What I'm looking for is your design philosophy. I don't see one. Are you suggesting a coherent policy, or are you just trying to find ways to argue with my position?

I was going to your example of I/O module only.
However, and this is the part that seems to grind you, the I/O module would be on that one ODBC client.

This is the worst design I could possibly ever imagine. Basically, no rules on the i. Use DB2 as a big SQL database engine.

So the design is:
- no triggers, constraints, etc
- I/O module only
- I/O module is controlled, and executed on, the ODBC client.

I can't over-emphasize: worst possible choice. Wrong on so many levels, and completely anathema to all your other arguments.

Seriously, is this something you would use for your production data at your shop? Really? Because I'm not exaggerating when I say I would fire anyone who did this.

Joe

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.