RE: [KCFusion] deletes on database?

[Ryan Hartwich]

Title: Message

Adaryl,   Somewhere I interviewed or spoke with someone about this topic.  It was my understanding that the individual coders being employed were generally not allowed to do any form of insert/update/delete into the database through their code.  They were however permitted to write Select statements to tables and/or views.   The coders were given a set of API calls utilizing XML services internally to do the direct DB manipulation.  The idea was to force data integrity and consistency by only allowing data to be modified through approved prebuilt modules.   A permutation of this would be to not permit inline DB calls in your CF code and to call all DB statements via stored procedures.  I have heard this speeds up development, improves reusability, and quality.  I'm a bit skeptical of this however.  I have spent a few years writing code as the primary developer and write my SQL code directly inside of my CF pages.  At least for small development teams with ad-hoc design standards that change frequently I think the extra overhead of standardizing and separating the layers adds significant complexity.  However, I would love to hear from those who have used this method in large, formal design groups.  It may be the way to go.   Ryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Adaryl Wakefield Sent: Wednesday, September 11, 2002 10:10 PM To: [EMAIL PROTECTED] Subject: [KCFusion] deletes on database? I once saw a job announcement that said something to the effect. "..no deletes on the database will be allowed. All deletes are done via XML..." At the time I just raised my eyebrow and went on but now I'm kinda curious if anybody can shed some light on what exactly they meant. I only have an academic understanding of XML and a small one at that. A.