|
From: | Alaric Snell-Pym |
Subject: | Re: [Chicken-users] DBI |
Date: | Thu, 28 Feb 2008 11:43:51 +0000 |
On 27 Feb 2008, at 8:11 pm, John Cowan wrote:
In reality, though, I think portability between databases is more hypothetical than real. Projects typically start with one database and stick to it, for moving between databases *even if a portability layer is in use* turns out to be hard -- all sorts of stuff outside the main code base ends up changing (path names, load scripts, whatever).
Yeah, but finer-grained things than apps can be portable. Eg, OR mapping layers. Being general-purpose tools, they want to be able to work on lots of different SQL servers, so the authors of them often avoid server-specific SQL, and where they have to for efficiency or whatever, make a decision what syntax to use there and then in that one place. So they benefit from a generic interface for the bulk of their queries. ABS -- Alaric Snell-Pym Work: http://www.snell-systems.co.uk/ Play: http://www.snell-pym.org.uk/alaric/ Blog: http://www.snell-pym.org.uk/?author=4
[Prev in Thread] | Current Thread | [Next in Thread] |