On 10/24/2014 5:26 PM, Matt Olson wrote:

My only problem with this, is if you go the SQL route within your RPG programs the code is atrocious. To many cursors and /EXEC SQL commands.

I feel like if your going to modernize your database, then you may as well pick a new language for your programs that can speak SQL better than the myriad of cursors and /EXEC SQL commands in an RPG program can do.

I think I could understand your argument better if I understood your
assumptions. I *think* I'm hearing you say that 'modernise' means 'move
to DDL and DML but leave the tables and their relationships as-is.'

Yeah, that'd be atrocious.

How about designing a new database, one with set-at-a-time access as the
base assumption? How about some brand new RPG programs with few if any
F-specifications and all of the access done via modern SQL using views
instead of contorted multi-way JOINs burned into the code? Or stored
procedures, shared with the web clients?

That's the route I've taken, along with triggers to keep the new
database in synch with the old, during the switch-over time. That seems
like a more workable definition of 'modern' to me.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.