From: Robert Buels Date: Fri, 4 Sep 2009 00:41:56 +0000 (+0000) Subject: couple of comment/documentation tweaks to pg storage driver X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=6ff1d58c2c54a9c8e0de435894b7944aaddc13c5;p=dbsrgits%2FDBIx-Class-Historic.git couple of comment/documentation tweaks to pg storage driver --- diff --git a/lib/DBIx/Class/Storage/DBI/Pg.pm b/lib/DBIx/Class/Storage/DBI/Pg.pm index b3d88f2..b11ace2 100644 --- a/lib/DBIx/Class/Storage/DBI/Pg.pm +++ b/lib/DBIx/Class/Storage/DBI/Pg.pm @@ -39,6 +39,7 @@ sub _dbh_last_insert_id { } +# get the postgres search path, and cache it sub _get_pg_search_path { my ($self,$dbh) = @_; # cache the search path as ['schema','schema',...] in the storage @@ -173,8 +174,8 @@ This class implements autoincrements for PostgreSQL. =head1 POSTGRESQL SCHEMA SUPPORT This supports multiple PostgreSQL schemas, with one caveat: for -performance reasons, the schema search path is queried the first time it is -needed and CACHED for subsequent uses. +performance reasons, data about the search path, sequence names, and +so forth is queried as needed and CACHED for subsequent uses. For this reason, you should do any necessary manipulation of the PostgreSQL search path BEFORE instantiating your schema object, or as