NAME
Dancer2::Session::DatabasePlugin - Dancer2 Session implementation for databases
SYNOPSIS
use Dancer2;
use Dancer2::Plugin::Database;
use Dancer2::Plugin::SessionDatabase;
DESCRIPTION
This class extends Dancer2::Core::Role::SessionFactory, and makes use of Dancer2::Plugin::Database for managing database connections.
CONFIGURATION
The session should be set to "DatabasePlugin" in order to use this session engine in your Dancer2 Application.
session: "DatabasePlugin"
engines:
session:
DatabasePlugin:
cache: 1 # default 1, when 0 statement handles are not cached
connection: "foo"
session_table: "SESSIONS"
id_column: "SESSION_ID"
data_column: "SESSION_DATA"
cache_sth: 1 # default 1, when set to 0 statement handles are not cached
plugins:
Database:
connections:
foo:
driver: "SQLite"
database: "foo.sqlite"
Expected Schema
The code was developed to use a table with 2 columns: SESSION_ID, SESSION_DATA, additional columns will not impact the code. No records are deleted unless the session destroy is called, so cleanup is something that may need to be done over time.
The sql statements are generated based on the configuration options, session_table, id_column, and data_column.
Example Schema
Testing and development was done using SQLite3.
Create statement is as follows:
create table sessions (session_id varchar unique,session_data blob);
How Queries are generated
All queries are generated using sprintf statements against constatins.
Column SESSION_ID
This column must have constraint defining the values as unique. The id is a string representing the current session, internals from Dancer2::Core::Session seems to return a 32 byte long string. It is highly recommended this column be indexed.
Column SESSION_DATA
This field is expected to be a BLOB or binary data type, although a large text field should work. The data being written to this column is generated by using Storable::nfreeze($ref).
SQL Statements
All SQL Statements are generated based on the given configuration.
Insert
Default Query Shown:
INSERT into SESSIONS (SESSION_ID,SESSION_DATA) values (?,?)
Sprintf Template:
INSERT into %s (%s,%s) values (?,?)
Update Existing session
Default Query Shown:
UPDATE SESSIONS SET SESSION_DATA=? WHERE SESSION_ID=?
Sprintf Template:
UPDATE %s SET %s=? WHERE %s=?
Delete
Default Query Shown:
DELETE FROM SESSIONS WHERE SESSION_ID=?
Sprintf Template:
DELETE FROM %s WHERE %s=?
SELECT Current Session
Default Query Shown:
SELECT SESSION_DATA FROM SESSIONS WHERE SESSION_ID=?
Sprintf Template:
SELECT %s FROM %s WHERE %s=?
SELECT All Session Keys
Default Query Shown:
SELECT SESSION_ID FROM SESSIONS
Sprintf Template
SELECT %s FROM %s
Rename Session
Default Query Shown:
UPDATE SESSIONS SET SESSION_ID=? WHERE SESSION_ID=?
Sprintf Template:
UPDATE %s SET %s=? WHERE %s=?
Dancer2::Plugin::Database hooks
This package makes use of hooks provdied by Dancer2::Database::Plugin.
"database_connection_lost"
This hook is used to clear the existing database statement handle cache.
"database_error"
This hook is used to clear the existing database statement handle cache.
Notes
Database Acces Pre-Fork
If you access sessions preforking, you will need to reset the statement handle session cache.
Example:
Clearing the Statement Handle Cache
The following code snippit will reset the built in statement handle cache to empty.
%{$Dancer2::Session::DatabasePlugin::CACHE}=();
Clearing the Database Connection
To release the current database session, use the following code snippet.
$Dancer2::Plugin::SessionDatabase::DBH=undef;
Specal Examples
Changing the freeze and thaw functions
Your database may not support globs or glob syntax, when this is the case it is possible to set a new subrouteens in place that handle the freezing and thawing of data.
Freeze
The nfreeze code reference is stored here
$Dancer2::Session::DatabasePlugin::FREEZE
Thaw
The thaw code reference is stored here
$Dancer2::Session::DatabasePlugin::THAW
Oracle in general
Oracle has some odd quirks, here is an example configuration that may help solve more than a few problems.
Database:
connections:
myoracledb:
driver: "Oracle:(DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = my.oracle.server.com)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME=ORACLE.SERVICE.COM)))"
username: OracleUser
password: 'xxxxxxx'
dbi_params:
RaiseError: 1
AutoCommit: 1
FetchHashKeyName: 'NAME_uc'
LongReadLen: 1000000
The manual bind example ( Oracle and the like )
Some databases require manual binds for blob. Here is an example of how to do this for Oracle.
use DBD::Oracle qw(:ora_types);
use Dancer2;
use Dancer2::Plugin::Database;
use Dancer2::Plugin::SessionDatabase;
$Dancer2::Session::DatabasePlugin::HANDLE_EXECUTE=sub {
my ($name,$sth,@bind)=@_;
if($name eq 'create_update_query') {
my ($string,$id)=@bind;
$sth->bind_param(1,$string,{ora_type => ORA_BLOB });
$sth->bind_param(2,$id,{ora_type => ORA_VARCHAR2});
$sth->execute();
} elsif($name eq 'create_flush_query') {
my ($id,$string)=@bind;
$sth->bind_param(1,$id,{ora_type => ORA_VARCHAR2});
$sth->bind_param(2,$string,{ora_type => ORA_BLOB });
$sth->execute();
} else {
$sth->execute(@bind);
}
};
Completly Changing an SQL statement
Sometimes you may want to replace the query created with something entierly new. To do this you will need to set $HANDLE_SQL_STRING function refrerence.
use Dancer2;
use Dancer2::Plugin::Database;
use Dancer2::Plugin::SessionDatabase;
$Dancer2::Session::DatabasePlugin::HANDLE_SQL_STRING=sub {
my ($name)=@_;
if($name eq 'query_to_alter') {
$_[1]='some new sql statement';
}
};
DBD::Sybase MSSQL FreeTDS Example
This example represents how to deal with some of the strange limitations when connecting via MSSQL via DBD::Sybase with FreeTDS.
The limitations are as follows: DBD::Sybase does not support multiple open statement handls when AuttoCommit is true. DBD::Sybase doesn't handle placeholders properly, and has some issues with binary data as well.
Session Configuration
In our session configuration we need to do the following: Disable statement handle caching and turn off the standard query generation code for the following functions: [create_update_query,create_flush_query].
engines:
session:
DatabasePlugin:
connection: "myconnection"
session_table: "SESSIONS"
id_column: "SESSION_ID"
data_column: "SESSION_DATA"
# Disable Caching of Statement handles
cache: 0
# skip internal Statment handler creation code for the following
no_create:
create_update_query: 1
create_flush_query: 1
Database Configuration
Our example database has AutoCommit Disabled.
plugins:
Database:
connections:
socmon:
driver: Sybase
server: SOCMON_DEV
username: username
password: xxx
database: myconnection
dbi_params:
RaiseError: 1
AutoCommit: 1
FetchHashKeyName: 'NAME_lc'
MSSQL Table Creation
MSSQL has some odd quirks when it comes to binary data, so in this case we will use varchar(max).
create table SESSIONS (
session_id varchar(32) ,
session_data varchar(max),
l astUpdate TimeStamp,
CONSTRAINT AK_session_id UNIQUE(session_id)
)
Code Example
Finnaly in your Dancer2 App we add the following code.
use JSON qw(to_json from_jsom);
$Dancer2::Session::DatabasePlugin::FREEZE=\&to_json;
$Dancer2::Session::DatabasePlugin::THAW=\&from_json;
$Dancer2::Session::DatabasePlugin::HANDLE_EXECUTE=sub {
my ($name,$sth,@bind)=@_;
if($name eq 'create_update_query') {
my ($string,$id)=@bind;
$string=~ s/'/''/g;
$id=~ s/'/''/g;
$Dancer2::Plugin::SessionDatabase::DBH->do("update sessions set session_data='$string' where session_id='$id'");
} elsif($name eq 'create_flush_query') {
my ($id,$string)=@bind;
$string=~ s/'/''/g;
$id=~ s/'/''/g;
$Dancer2::Plugin::SessionDatabase::DBH->do("insert into sessions (session_data,session_id) values ('$string','$id')");
} else {
$sth->execute(@bind);
}
};
See Also
Dancer2::Plugin::Database Dancer2::Session::YAML
LICENSE
This softare is distributed under the Perl 5 License.
AUTHOR
Michael Shipper <AKALINUX@cpan.org>