hstore

I'm working on a project that needs to use hstore on multiple schemas. The 'public' schema, where the hstore extension was being installed isn't available everywhere, because my scope doesn't lookup at 'public'. On some tryouts, I've created the extension on a schema called 'hstore' and used the schema on every available scope (search path) used. Based on this, I've some questions: Is it ok to create a schema just for the extension? Or is it better to create the extension on every single schema (like, customer_1 , customer_2 , and so on...)? Does the creation of the extension in a separate

Using PostgreSQL, column values from a table for 1st record are stored in a record variable. for ex: let the variable be: recordvar recordvar.columnname gives the value of the column name specified. I will define the columname in a variable: var := columnname In place of columnname if I replace with the variable i.e. recordvar.var , it is not working. Please let me know how to proceed in this situation. Following is the sample code: CREATE OR REPLACE FUNCTION getrowdata(id numeric, table_name character varying) RETURNS SETOF void AS $BODY$ DECLARE srowdata record; reqfield character varying;

Recently I went into trouble trying to use hstore with Django. I installed hstore this way: $ sudo -u postgres psql postgres=# CREATE EXTENSION hstore; WARNING: => is deprecated as an operator name DETAIL: This name may be disallowed altogether in future versions of PostgreSQL. CREATE EXTENSION postgres=# \dx List of installed extensions Name | Version | Schema | Description ---------+---------+------------+-------------------------------------------------- hstore | 1.0 | public | data type for storing sets of (key, value) pairs plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language (2 rows