Re: Re: State of Scala database access?

On 19 April 2011 18:50, Jim Powers <jim@casapowers.com> wrote:

On Tue, Apr 19, 2011 at 1:41 PM, Kevin Wright <kev.lee.wright@gmail.com> wrote:

The problem is that "rare situations" are common everyday occurrences, these tools need adaptors for each and every database to do even trivial stuff.
VARCHAR vs VARCHAR2 anyone?

Sadly yes.  There just seem to be way too many idiosyncrasies between DBs, they types they use, support for cursors, SPs, etc. to abstract away nicely.  My latest incarnation of "DB library thingy to make things more pleasant in Scala-land" is to just pimp the hell out of good-ol' JDBC and friends (connection poolers, for instance) and leave most of JDBC out in the open.  Sad, but true.

Hey, don't get me started on column-name quoting and case sensitivity :)

 

--
Jim Powers

--
Kevin Wright

gtalk / msn : kev.lee.wright@gmail.comkev.lee.wright@gmail.commail: kevin.wright@scalatechnology.com
vibe / skype: kev.lee.wrightquora: http://www.quora.com/Kevin-Wright
twitter: @thecoda

"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra