[Phplib-trackers] [ phplib-Bugs-550100 ] ct_sql/ac_get_lock() MySQL-only

[<no...@so...>]

Bugs item #550100, was opened at 2002-04-29 20:34
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=403611&aid=550100&group_id=31885

Category: None
Group: 7.4pre1
Status: Open
Resolution: None
Priority: 5
Submitted By: Richard Archer (richardarcher)
Assigned to: Nobody/Anonymous (nobody)
Summary: ct_sql/ac_get_lock() MySQL-only

Initial Comment:
What is this MySQL-dependent code doing in the ct_sql
class? At a minimum this should be abstracted via the
db_*_sql classes. But since MySQL is (AFAIK) the only
database to implement application-level locks, this is
difficult.

Really, this should be implemented in a manner
independent of both databases and storage containers. 

Having a separate table with a key of the session id or
application name and inserting/deleting rows in thaw()
and freeze() would seem appropriate. That would be
quite flexible, offering a way of single-threading both
the entire application and a single session. 

My pseudo-locking code in the -devel db_odbc.inc may be
a good base for this.

I don't think changing the API for this function would
matter. It has never actually worked, so we can't break
existing installations.


----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=403611&aid=550100&group_id=31885