Contents
-
Terminally Deprecated Elements
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 ordinary
Map (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 a
TransactionListener.
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 ordinary
Map (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 a
TransactionListener.
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 ordinary
Map (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 a
TransactionListener.
This class (a) isn't exposed in
pljava-api, (b) is only
used to implement the once-transactional attribute map in
Session,
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
a
TransactionListener to be kept in sync with transactions.
-
Deprecated Classes
This class (a) isn't exposed in
pljava-api, (b) is only
used to implement the once-transactional attribute map in
Session,
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
a
TransactionListener to be kept in sync with transactions.
-
Deprecated Methods
As of 1.5.0, this method is retained only for compatibility
with old code, and returns the same value as
getOuterUser, 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 of
SET 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.
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.
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 ordinary
Map (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 a
TransactionListener.
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 ordinary
Map (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 a
TransactionListener.
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 ordinary
Map (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 a
TransactionListener.
This seems never to have been used in git history of project.