I get the same result (1.84467440737096e+19) locally and on the live server.
I'm not sure how much i need for my data (i'm good with db, but not quite a 'guru' yet), but the db file size, when dumped, is only 400kb. The db interfaces (mysql-query-browser and phpmyadmin) show datasize total of 1.8MiB, and overhead total of 392.4KiB (this is only due to 1 table: the bug reports table).
The genealogy can go infinitely deep, but right now it is only 5 tiers/levels deep.
BTW, i changed the perms on the live server temporarily to let me connect via my home ip, and used the gui client to access it, and was able to lock it up via the same 3 commands as before (begin, set timezone, call procedure, locked up).
I will read the link you gave in your next post.
Thanks again.
----
I just glanced at the page, and noticed the nature of the topic, and realized why you linked to it, so i figured i'd throw this out there too:
When viewing from the TOP to Bottom of the tree/hierarchy, it can go infinitely deep (until there are no more members to pull); but from the Bottom going UP, it stops when it reaches the 'root'/system account. So, the tree can grow infinitely, but the functions stop when they hit the top or bottom. Bottom-Up and Top-Down are the differences in who is looking at it. Top-Down is a user who wants to see their tree; Bottom-Up is the system trying to figure out who gets what for commissions (per the payout algorithm). But both ways have a hard limit in the functions where clauses (at least, they SHOULD, but heck, i am only human, so i might be over looking something...).
premium domain names that i'm selling