NYCPHP Meetup

[Mitch Pirtle]

On 10/27/05, Hans Zaunere <lists at zaunere.com> wrote:
>
> Ahh, good old NSM...
>
> New York PHP developed an implementation of NSM, pNSM, as part of the clew
> project.

Then let's start that discussion over here, about the performance
benefits that turn into performance hits when your one table has 300
million rows...

Seriously, this concept makes lots of things seem easier, but next
thing you know, you got a really looooooong table on your hands and
only Oracle (IIRC) can partition across tablespaces at the table
level.

What to do when your nested table becomes more than you can manage? Is
it time then to go back to a more normalized model, or is this an
indication that - before you even implement - you have to take the
eventual number of rows that your nested table might have to manage?

-- Mitch, loving database discussions for a change ;-)