Deprecated API

Contents

  • For Removal
    Element Description
    org.postgresql.pljava.Session.executeAsSessionUser​(Connection, String)
    As of 1.5.0, this method is retained only for compatibility with old code, and has the same effect as executeAsOuterUser, which should be used instead. Previously, it used 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 uses only the session ID should be reported as an issue.
    org.postgresql.pljava.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 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.
    org.postgresql.pljava.Session.getSessionUserName()
    As of 1.5.0, this method is retained only for compatibility with old code, and returns the same value as getOuterUserName, 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.
    org.postgresql.pljava.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 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.
    org.postgresql.pljava.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 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.
  • Methods
    Method Description
    org.postgresql.pljava.Session.executeAsSessionUser​(Connection, String)
    As of 1.5.0, this method is retained only for compatibility with old code, and has the same effect as executeAsOuterUser, which should be used instead. Previously, it used 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 uses only the session ID should be reported as an issue.
    org.postgresql.pljava.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 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.
    org.postgresql.pljava.Session.getSessionUserName()
    As of 1.5.0, this method is retained only for compatibility with old code, and returns the same value as getOuterUserName, 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.
    org.postgresql.pljava.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 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.
    org.postgresql.pljava.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 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.