[Rails-core] Re: db:fixtures:load order

2007-07-30 Thread Hendy Irawan
Tarmo Tänav wrote: > On L, 2007-07-28 at 13:04 +0700, Hendy Irawan wrote: > >> Tarmo Tänav wrote: >> >>> I'm not actually proposing a mixed system, I'd just like a way to >>> load the fixtures like they are currently loaded but do it once >>> and only once for all tests. >>> >>> >>>

[Rails-core] Re: db:fixtures:load order

2007-07-30 Thread Tarmo Tänav
On E, 2007-07-30 at 15:45 +0700, Hendy Irawan wrote: > Do you know any plugin which provide this behavior (i.e. disable > constraints in Mysql/postgres/etc before fixture load, and enable them > after fixture load successful, for every test case?) > > Or you have one? > > It'd be deadly useful!!

[Rails-core] Re: db:fixtures:load order

2007-07-30 Thread pedz
Sorry for the confusion. I wasn't asking about your patch. I was asking about the original question posted by dailer. His changes, seems to me, makes most (all) of this other discussion pointless. Just add all your records in one transaction and be done with it -- at least with my current const

[Rails-core] Re: Fix to make has_one/has_many :dependent behaviour consistent (my first patch)

2007-07-30 Thread Chris Mear
Hey Pete, Looks like a good patch, but I think they're already discussing the issue here: http://dev.rubyonrails.org/ticket/7309 It certainly seems to cover some of the same ground (must admit I haven't looked into it in too much detail). Maybe check that ticket out and see if there's anything

[Rails-core] Re: Edge Rails namespaced routing

2007-07-30 Thread Peter
Hello again, For information purposes I wanted to follow up on this discussion with an already existing solution in edge. map.resources :customers do |ns| ns.namespace(:customers) do |customers| customers.resources :tags end end GET/customers/ {:action=>"index", :controller=>"custom

[Rails-core] Re: Fix to make has_one/has_many :dependent behaviour consistent (my first patch)

2007-07-30 Thread Pete Yandell
On Jul 30, 10:37 pm, Chris Mear <[EMAIL PROTECTED]> wrote: > Looks like a good patch, but I think they're already discussing the > issue here: > > http://dev.rubyonrails.org/ticket/7309 Saw that, but it only addresses has_many relationships, and changes the default behaviour when :dependent isn't