Re: [PHPLIB] active_sessions From: Kristian Koehntopp (kris <email protected>)
Date: 11/10/99

On Tue, Nov 09, 1999 at 05:08:53PM -0500, Charles P. Wright wrote:
> I use phplib for use with IMP 2.2.0-pre5, and have been having problems
> when I logout because of active_sessions updates being interspersed.
> Attached is code that I've tested with MySQL that uses replace instead of
> update or insert, this shoud make the update atomic and prevent nastiness.
> I don't have any other database servers, so I don't know if this fix is
> MySQL specific, but hopefully someone else will find it useful.

PHPLIB originally used replace instead of insert/update, but
that is MySQL specific and cannot be used with other databases.
In the meantime I have come to the conclusion that all database
operations are database specific and that we should be moving to
ct_sql__mysql.inc, ct_sql_informix.inc, ct_sql_oracle.inc and so
on and use the proper, database specific database update
operations. This has not been done, yet, though.

This will break compatibility in some way. The next release of
PHPLIB will break compatibility in a big way anyway, to
facilitate a general code cleanup and to be able to add support
for PHP4. We will no longer have different versions of the
active_sessions and auth_user tables, with and without support
for split sql or md5 encoded passwords, but there will be new,
unified tables which can to one or the other without changes.
The column names will change, too, to resolve any outstanding
namespace issues (we'll be adding column name prefixes).

If you are interested into discussion of such issues, or if you
want to contribute code, please subscribe to the developers
list, phplib-dev <email protected> I want to hear your opinions
about such compatibility issues before we break everything, that
is, the time to raise your voice is NOW (on the -dev list,
please!).

Kristian

-
PHP3 Base Library Mailing List. Send messages to <phplib <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-request <email protected>> in
the body, not the subject, of your message.