libdbix-safe-perl 1.2.5-4 source package in Ubuntu
Changelog
libdbix-safe-perl (1.2.5-4) unstable; urgency=medium * Remove re-generated file via debian/clean. (Closes: #1045263) * Add /me to Uploaders. * Declare compliance with Debian Policy 4.6.2. * Set Rules-Requires-Root: no. * Annotate test-only build dependencies with <!nocheck>. -- gregor herrmann <email address hidden> Tue, 05 Mar 2024 00:31:13 +0100
Upload details
- Uploaded by:
- Debian Perl Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Perl Group
- Architectures:
- all
- Section:
- perl
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Oracular | release | universe | perl | |
| Noble | release | universe | perl |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libdbix-safe-perl_1.2.5-4.dsc | 2.3 KiB | b73cdadcefcd8ee3549324ad2c7866ea4d180f06ec2b60564a650c73bbcd0986 |
| libdbix-safe-perl_1.2.5.orig.tar.gz | 16.6 KiB | 73279fd98b20034d3735dee67e2b89ac63d55449c3c64dd1a7ba0df10fbe0acf |
| libdbix-safe-perl_1.2.5-4.debian.tar.xz | 3.4 KiB | 6751e1b4414fe2ae36a8f2f57e9a5a426a434ff1f56161f6aee4ddcabb00a5f1 |
Available diffs
- diff from 1.2.5-3 to 1.2.5-4 (1.0 KiB)
No changes file available.
Binary packages built by this source
- libdbix-safe-perl: safe wrapper to DBI interface
The purpose of the DBIx::Safe module is to give controlled, limited access to
an application, rather than simply passing it a raw database handle through
DBI. DBIx::Safe acts as a wrapper to the database, by only allowing through
the commands you tell it to. It filters all things related to the database
handle - methods and attributes.
.
The typical usage is for your application to create a database handle via a
normal DBI call to new(), then pass that to DBIx::Safe->new(), which will
return you a DBIx::Safe object. After specifying exactly what is and what is
not allowed, you can pass the object to the untrusted application. The object
will act very similar to a DBI database handle, and in most cases can be used
interchangeably.
.
By default, nothing is allowed to run at all. There are many things you can
control. You can specify which SQL commands are allowed, by indicating the
first word in the SQL statement (e.g. 'SELECT'). You can specify which
database methods are allowed to run (e.g. 'ping'). You can specify a regular
expression that allows matching SQL statements to run (e.g. 'qr{SET
TIMEZONE}'). You can specify a regular expression that is NOT allowed to run
(e.g. qr(UPDATE xxx}). Finally, you can indicate which database attributes
are allowed to be read and changed (e.g. 'PrintError'). For all of the above,
there are matching methods to remove them as well.
