Re: Using Sequel::Model with namespaced classes

2008-05-16 Thread Xavier Lange
It looks like ARAI Shunichi found this bug as well. I was able to push my way through and continue working but I have hit another dataset problem. How can I use a polymorphic many_to_many relationship if Sequel::Model wants to use the join model's name as quantifier in the where statement? Both

Re: MAJOR changes: Make identifier quoting optional, quote all identifiers, force explicit table aliasing when joining

2008-05-16 Thread Jeremy Evans
On May 15, 11:55 pm, Farrel [EMAIL PROTECTED] wrote: In that case I'll probably have to go back to using the stable 1.5.1 gems. Is there any chance of a 1.5.2 release with before_validations support soon? That was the only reason I was using the latest source. No. There have been a lot of

Re: Using Sequel::Model with namespaced classes

2008-05-16 Thread Jeremy Evans
On May 16, 12:30 am, Xavier Lange [EMAIL PROTECTED] wrote: It looks like ARAI Shunichi found this bug as well. I was able to push my way through and continue working but I have hit another dataset problem. How can I use a polymorphic many_to_many relationship if Sequel::Model wants to use

Re: Using Sequel::Model with namespaced classes

2008-05-16 Thread Jeremy Evans
On May 16, 9:53 am, Xavier Lange [EMAIL PROTECTED] wrote: One of your errors may be you got the order of things mixed up, it should be like this: class Factor ItemContainer set_dataset Sequel::Model.db[:item_containers].where{:kind == 'Factor'} dataset.set_model(:kind, Hash.new {|h,

Support for additional multi methods and SQL statement options

2008-05-16 Thread Mark V
Hi Devs, I'd appreciate any voices for/against the following. I'd like to add multi_update, multi_insert!. In the process it became clear there is lots of parsing of an 'args' array that this would have to get factored out, see http://pastie.caboo.se/198077 Further, the multi_insert_sql, and