| List: | Falcon Storage Engine | « Previous MessageNext Message » | |
| From: | Vladislav Vaintroub | Date: | March 19 2009 11:50pm |
| Subject: | RE: New Transaction State object (Was: Problems with record visibility and how it is computed) | ||
| View as plain text | |||
> -----Original Message----- > From: Jim Starkey [mailto:jstarkey@stripped] > Sent: Thursday, March 19, 2009 11:35 PM > To: Olav Sandstaa > Cc: FalconDev > Subject: Re: New Transaction State object (Was: Problems with record > visibility and how it is computed) > It occurred to me that we need the active transaction list to track > down > transaction that have updates to tables that the MySQL server wants to > delete. I don't see anyway around it, at least not for now. I suggest > we put this dream aside until less strenuous times. I think it is MySQL server's job not to allow a drop on a table with active transactions. Any storage engine would benefit from that. And maybe it is already done, I do not know . Forwarding to Kostja requesting more info on subject and hoping for qualified answer. Vlad > -- > Jim Starkey > President, NimbusDB, Inc. > 978 526-1376 > > > -- > Falcon Storage Engine Mailing List > For list archives: http://lists.mysql.com/falcon > To unsubscribe: http://lists.mysql.com/falcon?unsub=1