|
... | which returns the next | available transaction number as a string. Then, the users of the | procedure are spared the gory details of the actual implementation.
What advantage does a procedure offer in this case...?
Well, that depends...
I try to design systems where the links between business, UI, program code, and database are kept to a minimum (and I believe most good 400 architects do also.) So I like a database that is updated in as minimal number of programs/modules as possible... Ideally, there would be between 1 and 3 places the transaction number would be incremented and updated, in the first place. ...
... I wish you could tutor me in Python some more!
As an Amazon Associate we earn from qualifying purchases.
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.