Everything

php

session.save_handler=sqlite must go

php.internals

Kevin Waterson

20 years ago

I have played with this and it looks a good idea on paper
but have not been successful in practice. If this is not
going to work easily, lets remove the option for session.save_handler
tis a silly idea.

Kevin

--
"Democracy is two wolves and a lamb voting on what to have for lunch.
Liberty is a well-armed lamb contesting the vote."

Wez Furlong

20 years ago

Care to elaborate?
It work(ed) just fine.  It may not be the fastest thing in the world,
but not every application requires raw speed.

--Wez.

On 10/12/05, Kevin Waterson <kevin@oceania.net> wrote:

Kevin Waterson

20 years ago

This one time, at band camp, Wez Furlong <kingwez@gmail.com> wrote:

> Care to elaborate?

When using session.save_handler=files all works fine using /tmp
If this is changed to sqlite, I get errors cannot write to /tmp

Kind regards
Kevin

--
"Democracy is two wolves and a lamb voting on what to have for lunch.
Liberty is a well-armed lamb contesting the vote."

Wez Furlong

20 years ago

Then maybe you should try specifying the path to the file that you
want it to create, rather than the dir in which to create it.

--Wez.

On 10/12/05, Kevin Waterson <kevin@oceania.net> wrote:

Antony Dovgal

20 years ago

On 12.10.2005 23:36, Kevin Waterson wrote:

> This one time, at band camp, Wez Furlong <kingwez@gmail.com> wrote:
>
>> Care to elaborate?
>
> When using session.save_handler=files all works fine using /tmp
> If this is changed to sqlite, I get errors cannot write to /tmp

Please use php-general@lists.php.net for such questions.
If something doesn't work for you, your first thought should be "what am I doing wrong" and not "this thing doesn't work and must go".

--
Wbr,
Antony Dovgal

John Coggeshall

20 years ago

It works fine, but like SQLite has limitations on scalability.

John

On Wed, 2005-10-12 at 20:03 +1000, Kevin Waterson wrote: