-
For Removal Element Description org.postgresql.pljava.internal.Session.executeAsSessionUser(Connection, String) org.postgresql.pljava.internal.Session.getAttribute(String) Session
's attribute store once had a special, and possibly useful, transactional behavior, but since PL/Java 1.2.0 it has lacked that, and offers nothing you don't get with an ordinaryMap
(that forbids nulls). If some kind of store with transactional behavior is needed, it should be implemented in straight Java and kept in sync by using aTransactionListener
.org.postgresql.pljava.internal.Session.getSessionUserName() org.postgresql.pljava.internal.Session.removeAttribute(String) Session
's attribute store once had a special, and possibly useful, transactional behavior, but since PL/Java 1.2.0 it has lacked that, and offers nothing you don't get with an ordinaryMap
(that forbids nulls). If some kind of store with transactional behavior is needed, it should be implemented in straight Java and kept in sync by using aTransactionListener
.org.postgresql.pljava.internal.Session.setAttribute(String, Object) Session
's attribute store once had a special, and possibly useful, transactional behavior, but since PL/Java 1.2.0 it has lacked that, and offers nothing you don't get with an ordinaryMap
(that forbids nulls). If some kind of store with transactional behavior is needed, it should be implemented in straight Java and kept in sync by using aTransactionListener
.org.postgresql.pljava.internal.TransactionalMap This class (a) isn't exposed inpljava-api
, (b) is only used to implement the once-transactional attribute map inSession
, and (c) hasn't had transactional behavior even there, since 3ab90e5 (November 2005). Future code needing any kind of store sync'd to PostgreSQL transactions should implement that behavior with Java's ordinary tools, using aTransactionListener
to be kept in sync with transactions.
-
Classes Class Description org.postgresql.pljava.internal.TransactionalMap This class (a) isn't exposed inpljava-api
, (b) is only used to implement the once-transactional attribute map inSession
, and (c) hasn't had transactional behavior even there, since 3ab90e5 (November 2005). Future code needing any kind of store sync'd to PostgreSQL transactions should implement that behavior with Java's ordinary tools, using aTransactionListener
to be kept in sync with transactions.
-
Methods Method Description org.postgresql.pljava.internal.AclId.getSessionUser() As of 1.5.0, this method is retained only for compatibility with old code, and returns the same value asgetOuterUser
, which should be used instead. Previously, it returned the session ID unconditionally, which is incorrect for any PostgreSQL version newer than 8.0, because it was unaware ofSET ROLE
introduced in 8.1. Any actual use case for a method that ignores roles and reports only the session ID should be reported as an issue.org.postgresql.pljava.internal.ErrorData.isShowFuncname() The property queried by this method was only used in PostgreSQL when communicating with old clients over the v2 frontend/backend protocol, superseded in PostgreSQL 7.4. In PG 14 and later, there is no such property, and this method will always return false.org.postgresql.pljava.internal.Session.executeAsSessionUser(Connection, String) org.postgresql.pljava.internal.Session.getAttribute(String) Session
's attribute store once had a special, and possibly useful, transactional behavior, but since PL/Java 1.2.0 it has lacked that, and offers nothing you don't get with an ordinaryMap
(that forbids nulls). If some kind of store with transactional behavior is needed, it should be implemented in straight Java and kept in sync by using aTransactionListener
.org.postgresql.pljava.internal.Session.getSessionUserName() org.postgresql.pljava.internal.Session.removeAttribute(String) Session
's attribute store once had a special, and possibly useful, transactional behavior, but since PL/Java 1.2.0 it has lacked that, and offers nothing you don't get with an ordinaryMap
(that forbids nulls). If some kind of store with transactional behavior is needed, it should be implemented in straight Java and kept in sync by using aTransactionListener
.org.postgresql.pljava.internal.Session.setAttribute(String, Object) Session
's attribute store once had a special, and possibly useful, transactional behavior, but since PL/Java 1.2.0 it has lacked that, and offers nothing you don't get with an ordinaryMap
(that forbids nulls). If some kind of store with transactional behavior is needed, it should be implemented in straight Java and kept in sync by using aTransactionListener
.