On 13/05/2010, at 4:31 PM, Daryl Manning wrote:
So, the question I'd ask here is if you're using the right hammer
for the job.
Sounds like database design might be an issue here
...
On 13/05/2010, at 2:43 PM, Sean Seefried wrote:
To give you a brief taste the hierarchy roughly goes: local
government area, precinct, building type, consumption.
I wouldn't have tried putting such a fixed hierarchy into one table.
If the hierarchy is always four levels, use four tables.
It'll make your SQL easier, and probably your code gyrations too.
Clifford Heath, Data Constellation, http://dataconstellation.com
Agile Information Management and Design
--
You received this message because you are subscribed to the Google Groups "Ruby or
Rails Oceania" 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/rails-oceania?hl=en.
