Currently, when Sequel is used with some databases (such as MySQL), it
reuses connections when it shouldn't do so. For example, this will
cause problems on MySQL:
DB[:items].each{|x| DB[:items].each{|y| puts y == x}}
The issue is Sequel tries to reuse the same connection for both
selects, whic
On May 6, 8:18 am, ivanb <[EMAIL PROTECTED]> wrote:
> Hi.
> I have Postgres and I am having trouble accessing bytea field.
> I guess data doesn't get escaped the right way.
> How to do this? Is there something in connection string, or in model
> or where?
>
> I searched and searched and couldn't f
Hi.
I have Postgres and I am having trouble accessing bytea field.
I guess data doesn't get escaped the right way.
How to do this? Is there something in connection string, or in model
or where?
I searched and searched and couldn't find anything about this topic.
--~--~-~--~~--
On May 5, 10:39 am, notmuch <[EMAIL PROTECTED]> wrote:
> I am trying to call an oracle stored procedure, which returns a
> resultset(cursor) via an OUT parameter.
> I have tried several variations and could not find a way to bind(and
> retrieve) a value/variable to the parameter. Here's a raw temp
Congratulations for all Sequel developers!
I tried Directed Graph feature, and it's really powerful. I'm impressed.
P.S. new ruby-sequel.org site is little bit slow accessing from Japan.
-
Mellowtone Inc. - life is a melody
Shunichi Arai
http://www.mellowtone.co.jp
http://asiajin.com/blog/
