GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
Tangram::Driver::Pg(3) User Contributed Perl Documentation Tangram::Driver::Pg(3)

Tangram::Driver::Pg - Orthogonal Object Persistence in PostgreSQL databases

   use Tangram;
   use Tangram::Driver::Pg;

   $schema = Tangram::Driver::Pg->schema( $hashref );

   Tangram::Driver::Pg->deploy($schema, $dbh);

   $storage = Tangram::Driver::Pg->connect( $schema,
      $data_source, $username, $password );

   $storage->disconnect();

   Tangram::Driver::Pg->retreat($schema, $dbh);

This is the entry point in the Pg-specific object-relational persistence backend.

This module performs the following:

This backend does not add any methods; for a description of available methods, see Tangram::Relational.

Tangram::Type::Dump::Storable objects are first encoded with MIME::Base64, because Tangram does not currently have an easy mechanism for calling "DBI->bind_param()" at the appropriate time to flag the column as binary.

Tangram::Type::Dump::Perl objects are stored as "BYTEA" columns, which as of DBD::Pg 1.31, also do not get correctly escaped by the DBD driver. This also affects the (as-yet not fully functional) Tangram::Type::Dump::YAML back-end, which might put "\" characters into a YAML document.

It is recommended to use the "storable" type with Tangram::Type::Dump::Any for this reason.

2015-10-09 perl v5.32.1

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.