Re: [CFCDev] data abstraction layer ideas? - diff db's (was Serialization of CFCs)

[Ian Sheridan]

I would step back and instead of figuring out a coding solution, which 
might take a while to fully develop, think about  the requirements of 
the application and then require the the use of the DB that you made 
those 2000 SQL statements for. Then this would be the standard for the 
application where ever it is going to reside.

If you have to leave behind the legacy DB the time it would take to 
redo (most likely not all) the SQL, might still be shorter then the 
time it would take to develop a "generic" solution for multiple DBs.

Ian
On Jul 7, 2004, at 9:26 AM, Barry L Beattie wrote:
Each DB table has a CFC that relates to it
That's a bit hard for us to do. 140+ tables = 140+ CFC's just for data 
access. We also have the added complication that there's a lot of 
conditional logic to build either the SQL or the result sets - things 
that should be in joins (or in the T-SQL for SQLServer) but are 
wrapped up in a legacy db design (no varchars!). eg:

query for person, address in tableA
if (query for person in tableB)
  get tableB.address
  address = tableB.address
end if
if (query for person in tableC)
  get tableC.address
  address = tableC.address
end if
return person, address
so what I'm curious about are ideas that would allow us to use diff 
db's without resorting to re-writing nearly 2000 queries for each db 
vendor.

any suggestions?
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' 
in the message of the email.

CFCDev is run by CFCZone (www.cfczone.org) and supported
by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]