[Nitro] [PATCH] Allow multiple joins_many style relationships between two classes (and relevent test case)

Bryan Soto bryan.a.soto at gmail.com
Fri Feb 17 15:48:42 EST 2006

Just a quick note. After this is applied, there is a new test failure:

  1) Failure:
    [./test/og/tc_store.rb:263:in `features_test'
     ./test/og/tc_store.rb:76:in `test_og']:
<1> expected but was

I'll try and check it out later.

On 2/17/06, Rob Pitt <rob at motionpath.com> wrote:
> WARNING: This patch causes join tables to be created with different
> names and will require you to manually copy join table data into newly
> named tables if applied to a project you are already using.
> Why would I make a patch that requires this? Not having this requirement
> (i.e. doing it in an automated fashion) would be fairly complicated and
> a big drain on CPU.
> This patch still needs to be implemented at some point because it
> enables a desirable behaviour, and we are at 0.2 so we should make
> changes with big impacts like this now rather than later.
> This is a very minor modification so that a model like this behaves as
> it should:
> Class Article
>   property :title, String
>   joins_many :first_join, Category
>   joins_many :second_join, Category
>   joins_many Category
>   def initialize(title)
>     @title = title
>   end
> end
> Without this patch, items you push into .first_join are visible
> in .second_join and the .categories join (all other combinations of this
> are also true).
> This is wrong, and this patch corrects this.
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/nitro-general/attachments/20060217/62051794/attachment.html 

More information about the Nitro-general mailing list