Starch::Store::DBIx::Connector - Starch storage backend using DBIx::Connector.
my $starch = Starch->new(
store => {
class => '::DBIx::Connector',
connector => [
$dsn,
$username,
$password,
{ RaiseError=>1, AutoCommit=>1 },
],
},
);
This Starch store uses DBIx::Connector to set and get state data.
The table in your database should contain three columns. This is the SQLite syntax for creating a compatible table which you can modify to work for your particular database's syntax:
CREATE TABLE starch_states (
key TEXT NOT NULL PRIMARY KEY,
data TEXT NOT NULL,
expiration INTEGER NOT NULL
)
This must be set to either an array ref arguments for DBIx::Connector or a pre-built object (often retrieved using a method proxy).
When configuring Starch from static configuration files using a method proxy is a good way to link your existing DBIx::Connector object constructor in with Starch so that starch doesn't build its own.
A Data::Serializer::Raw for serializing the state data for storage
in the "data_column". Can be specified as string containing the
serializer name, a hash ref of Data::Serializer::Raw arguments, or as a
pre-created Data::Serializer::Raw object. Defaults to JSON
.
Consider using the JSON
or Sereal
serializers for speed.
Sereal
will likely be the fastest and produce the most compact data.
The DBIx::Connector method to call when executing queries.
Must be one of run
, txn
, or svp
. Defaults to run
.
The connection mode to use
when running the "method". Defaults to undef
which lets
DBIx::Connector use whichever mode it has been configured to use.
Must be on of ping
, fixup
, no_ping
, or undef
.
Typically you will not want to set this as you will have provided a pre-built DBIx::Connector object, using a method proxy, which you've already called "mode" in DBIx::Connector on.
The table name where states are stored in the database.
Defaults to starch_states
.
The column in the "table" where the state ID is stored.
Defaults to key
.
The column in the "table" which will hold the state
data. Defaults to data
.
The column in the "table" which will hold the epoch time
when the state should be expired. Defaults to expiration
.
The SQL used to create state data.
The SQL used to update state data.
The SQL used to confirm whether state data already exists.
The SQL used to retrieve state data.
The SQL used to delete state data.
Set "remove" in Starch::Store.
Please submit bugs and feature requests to the Starch-Store-DBIx-Connector GitHub issue tracker:
https://github.com/bluefeet/Starch-Store-DBIx-Connector/issues
Aran Clary Deltac <bluefeet@gmail.com>
Thanks to ZipRecruiter for encouraging their employees to contribute back to the open source ecosystem. Without their dedication to quality software development this distribution would not exist.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.