Perl DBI to Ruby DBI?

[Bryan.La...@gmail.com]

is this easily transferable or would it be easier to code from
scratch? I read that the two were very similar...

[Bryan.La...@gmail.com]

and by transferable I mean if a driver written against the Perl DBI
can be easily put against the Ruby DBI.

On Jan 18, 2:23 pm, "Bryan.Lahartin...@gmail.com"

[Anthony Kelly]

I think that DBI is discouraged in general:

'Because DBI adds another layer of indirection, it will decrease
performance and you should avoid using it for ActiveRecord. Please, do
not misunderstand me: DBI is great but ActiveRecord needs as much
performance as possible, so use a native driver instead.'

Is there a native SQL Anywhere driver?

Thanks,
Anthony

On Jan 18, 2:25 pm, "Bryan.Lahartin...@gmail.com"

[Bryan Lahartinger]

thats what I'm supposed to make :) lol

[Anthony Kelly]

Oh ok lol. Would you consider making both?

That is a DBI one and then a non DBI one? If not that's ok too.

On Jan 21, 8:05 am, Bryan Lahartinger <Bryan.Lahartin...@gmail.com>
wrote:

[Bryan Lahartinger]

That is actually the plan that is in the works atm.

[Kiriakos Georgiou]

I have coded extensively with the perl DBI and I have to confess ruby
and sybct makes DBI look dated.
Perhaps that's down to ruby and its awesome iterators.

Kiriakos