Hi!
On Jul 12, 2008, at 9:47 AM, Mark Atwood wrote:
Your idea has a lot of merit. But engines have to have a way of
saying "i cant tell you if a table exists until you try to look for
it, and you cant trust your cache to be utterly sure that the table
still exists".
AKA a better discovery system. The issue I see though sits around
"show tables". If you open up 10K of tables for that command you do
not want them to persist beyond the scope of that command. We would
risk running out of memory.
The async message design has the advantage of not needing locks. A
general framework for that would be good for setting up a situation
where we would no longer need to do lock and tests all over the place.
Locks are the death of concurrency :)
Cheers,
-Brian
--
_______________________________________________________
Brian "Krow" Aker, brian at tangent.org
Seattle, Washington
http://krow.net/ <-- Me
http://tangent.org/ <-- Software
_______________________________________________________
You can't grep a dead tree.
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
