#636: Database session storage implementations have incorrect read/write
behavior
---------------------+------------------------------------------------------
Reporter: david | Owner: david
Type: defect | Status: new
Priority: normal | Milestone: 0.11.1
Component: storage | Version: 0.11.0
Severity: minor | Keywords:
---------------------+------------------------------------------------------
Handlers are not supposed to create a non-existing record on {{{read()}}}.
The original reasoning is likely that a {{{write()}}} this way can simply
perform an {{{UPDATE}}}, but apparently, {{{session_regenerate_id()}}}
will trigger a {{{write()}}} w/o {{{read()}}}. We should do it by the book
anyway:
Read function must return string value always to make save handler
work as expected. Return empty string if there is no data to read. Return
values from other handlers are converted to boolean expression. TRUE for
success, FALSE for failure.
--
Ticket URL: <http://trac.agavi.org/ticket/636>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
