On May 15, 12:00 am, Jeremy Evans <[EMAIL PROTECTED]> wrote:
> The traceback makes it look like this is an active_support problem.
> Assuming that this is happening with an association, try specifying
> the :class option as a string instead of using a constant.
> Alternatively, if you provide a tr
>
> Fixed using your
> idea:http://github.com/jeremyevans/sequel/commit/47f3c7d168cf2f6673a7302e6...
>
> Thanks for reporting this issue.
>
> Jeremy
nice. this fix also patches redirecting from inside transaction
which, in ramaze at least, is throw/catch based and causes the same
issue.
than
On May 14, 2:40 pm, "ara.t.howard" <[EMAIL PROTECTED]> wrote:
> just a quick note, this pattern is more robust, as it's possible to
> have something lying around in $!:
>
> error = nil
>
> begin
> yield
> rescue Object => error
> ensure
> if error
> handle_error
> else
> handle_succe
I just made some major changes to the master branch, which could break
some existing code. I don't do such a thing without a good reason, in
this case because I believe the current design was fatally flawed.
Three major changes have just been committed
1) Identifier (table/column) quoting is now
On May 14, 1:47 pm, Farrel <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Is there a merb_sequel maintainer? I have been getting the following
> errors whenever I try to do a migration on Merb:
There may be, but merb_sequel not maintained by the Sequel maintainer
(me). That may change in the future, i
I can set up the logging and emailing to sequel-talk.
The IRC channel would need have the MOD altered.
Should start in the next day or so.
Mark
On Thu, May 15, 2008 at 4:10 AM, Jeremy Evans <[EMAIL PROTECTED]> wrote:
>
>
> On May 14, 1:59 am, "Mark V" <[EMAIL PROTECTED]> wrote:
> > Hi Devs,
>
just a quick note, this pattern is more robust, as it's possible to
have something lying around in $!:
error = nil
begin
yield
rescue Object => error
ensure
if error
handle_error
else
handle_success
end
end
so, same idea, just avoid the global/thread-var $!.
cheers.
--~--~
Hi all,
Is there a merb_sequel maintainer? I have been getting the following
errors whenever I try to do a migration on Merb:
[EMAIL PROTECTED] ~/Projects/blue_mars/app/models $ rake
sequel:db:migrate
(in /home/farrel/Projects/blue_mars)
~ Loaded DEVELOPMENT Environment...
~ loading gem 'merb_
On May 14, 1:59 am, "Mark V" <[EMAIL PROTECTED]> wrote:
> Hi Devs,
> What are your thoughts on circulating, via the sequel-talk mail list,
> a log of the sequel IRC channel each 24 hrs?
> DataMapper does this and it can be handy way to review what has been
> discussed debated in the IRC channel.
>
On May 13, 8:50 pm, "ara.t.howard" <[EMAIL PROTECTED]> wrote:
> afaikt sequel suffers from this slippery bug:
>
> cfp:~/site/votelink.com > cat a.rb
> def (Db = Object.new).execute string
> puts string
> end
>
> def (UnSafe = Db.clone).transaction
> begin
> execute 'BEGIN'
> yield
>
Hi Devs,
What are your thoughts on circulating, via the sequel-talk mail list,
a log of the sequel IRC channel each 24 hrs?
DataMapper does this and it can be handy way to review what has been
discussed debated in the IRC channel.
My understanding is the freenode conditions require the channel
ow
11 matches
Mail list logo
