> It's only current limitation appears to be an inability to > deal with tables with more than one primary key.
By definition, a table can only have one primary key (which, of course, may consist of more than one field). Rails can't deal with compound keys, which is what I suspect you meant. As I recall, Rails expects tables to have plural names, and expects key fields to have specific names. I suspect those default expectations may be changeable, but many legacy databases don't even have a standard naming convention. > I ask that myself every time I wonder why CF doens't have a > database- agnostic layer built into CFQUERY. I'm not sure what you'd expect that to be like, exactly, but I can tell you why I suspect CF doesn't have what you're looking for - that's not the job of the language itself to implement. Rails is a framework, not part of Ruby proper. Ruby is a general-purpose programming language. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! This email has been processed by SmoothZap - www.smoothwall.net ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:274286 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
