[Tinymux] @query/sql

[Stephen Dennis]

I meant to encourage everyone with opinion.

Some games using sql() are experiencing a lag problems. They use it
often enough and they have enough players that it is creating
problems. That said, they also view many sql as inherently functional,
and also would like to keep the sql() interface.

So, I'm going to provide @sql, sql(), and @query. The first two will
use the @query plumbing. To the degree that using sql() creates
problems, these games can switch to @query to improve things.

But, if you aren't experiencing lag with sql(), this implementation to
sql() should do fine as well.

Brazil

On 11/23/05, Suzanne Baylor <sbaylor at dsl-only.net> wrote:
> Stephen Dennis wrote:
>
> >PennMUSH people need to speak out that they have a preference or it is
> >already implemented a particular way in one of their patches.
> >
> >
> >
> >
> You probably mean the coders but here is an end user perspective:
>
> I have some SQL code that reads and writes phpBB, Mantis, PMBox, and
> misc modules in a PostNuke environment. It uses the sql() and
> sql_escape() pretty much exclusively. I've never noticed a lag problem
> but its all on the same server and is mostly just me goofing around
> testing and learning.
>
> I also play on a Rhost game that uses SQL and has about 60 active folks
> RPing at a time that I believe calls SQL fairly often (+noms, looking up
> info, etc.) In a year and a half I think it was down twice. The rhost
> help command list looks similar to Penn's: sql(), sqlescape(), @sql,
> @sqlconnect, @sqldisconnect, sqlon(), sqloff().
>
> Also note that Penn's digest() encoding function was also very handy for
> checking user passwords stored up in the SQL database but that requires
> SSL for md5 encoding. (So add SSL to the list *grin*)
>
> Suzanne
> _______________________________________________
> Tinymux mailing list
> Tinymux at tinymux.org
> http://www.tinymux.org/mailman/listinfo/tinymux
>