On 17 June 2010 22:22, Marnen Laibow-Koser li...@ruby-forum.com wrote:
Toby Rodwell wrote:
...
If you don't have control of the database, you should not be doing the
project. Really.
I don't think this is a valid general point. There are often
situations involving a legacy database where it
Marnen Laibow-Koser wrote:
You want awesome_nested_set, which will let you do that with one query.
The Glue model is unnecessary.
Thanks very much for the info. I've had a quick look at the
documentation and I see it makes use of fields :lft and :rgt -I guess I
can use aliases for these,
Toby Rodwell wrote:
Marnen Laibow-Koser wrote:
You want awesome_nested_set, which will let you do that with one query.
The Glue model is unnecessary.
Thanks very much for the info. I've had a quick look at the
documentation and I see it makes use of fields :lft and :rgt -I guess I
Marnen Laibow-Koser wrote:
Toby Rodwell wrote:
Marnen Laibow-Koser wrote:
You may be able to use aliases, but how does this solve the basic
problem of adding fields to the DB?
I don't add fields (or even records) to this database - I just use RoR
as way a way to get data out in a useful
Toby Rodwell wrote:
Marnen Laibow-Koser wrote:
Toby Rodwell wrote:
Marnen Laibow-Koser wrote:
You may be able to use aliases, but how does this solve the basic
problem of adding fields to the DB?
I don't add fields (or even records) to this database - I just use RoR
as way a way to get
Toby Rodwell wrote:
I have a 'Circuit' table, and a 'Glue' table to perform a many-to-many
join on the circuit records, such at a circuit can have many subcircuits
(its component parts) and many supercircuits (circuits which it itself
is a part of).
In other words, you have a hierarchical
6 matches
Mail list logo
