On May 31, 10:34 pm, Marnen Laibow-Koser <rails-mailing-l...@andreas-
s.net> wrote:
> I think you will want to do this on the DB side rather than in the app.
> The various DB servers out there have ways of breaking up tables for
> performance reasons and still having them look the same to the
> application (I think MERGE tables in mySQL fit this description). So
> investigate what your DB server can do for you before you start trying
> to get clever with table-based subclasses.
>
> Best,
> --
> Marnen Laibow-Koserhttp://www.marnen.org
> [email protected]
> --
> Posted viahttp://www.ruby-forum.com/.
Oh! I hadn't even considered that. I will look into MERGE tables and
see if that's going to do what I need. I'm not set on this as the
best solution either, just running through possibilities and making
sure I don't exclude any reasonable options with poor design. I've
also put some thought into having specific tables groups of tables
hosted on other DB servers, but that is a much less mysterious
implementation so I didn't need to ask if anyone has tried it
before. :)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---
