psycopg2

Can anybody tell me how can I change database dynamically which I have created just now.. using the following code... I think during the execution of this code I will be in default postgres database (which is template database) and after new database creation I want to change my database at runtime to do further processing... from psycopg2 import connect from psycopg2.extensions import ISOLATION_LEVEL_AUTOCOMMIT dbname = 'db_name' con = connect(user ='postgres', host = 'localhost', password = '*****') con.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT) cur = con.cursor() cur.execute('CREATE

I've installed psycopg2 with pip install psycopg2 and it worked just fine. The install output had a couple of warning along the lines of In file included from ./psycopg/psycopg.h:33: ./psycopg/config.h:71:13: warning: unused function 'Dprintf' [-Wunused-function] static void Dprintf(const char *fmt, ...) {} ^ 1 warning generated. but in the end it says Successfully installed psycopg2 and it also appears when I run pip list . Now when I try to import it in python I get an error: $ python Python 2.7.5 (default, Aug 25 2013, 00:04:04) [GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)] on

I'm trying to use a server-side curser in psycop2 as detailed in this blog post . In essence, this is achieved with from django.db import connection if connection.connection is None: cursor = connection.cursor() # This is required to populate the connection object properly cursor = connection.connection.cursor(name='gigantic_cursor') When I execute the query: cursor.execute('SELECT * FROM %s WHERE foreign_id=%s' % (table_name, id)) I get a ProgrammingError : psycopg2.ProgrammingError: can't use a named cursor outside of transactions I've naively tried to create a transaction using cursor

I have a django app with version as 1.6.5 , i am trying to upgrade it to 1.8 , but on the way i got the below error right after the django version was increased to 1.8 There is no South database module 'south.db.postgresql_psycopg2' for your database. Please either choose a supported database, check for SOUTH_DATABASE_ADAPTER[S] settings, or remove South from INSTALLED_APPS. Code INSTALLED_APPS = [ 'django_messages', 'avatar', 'tinymce', 'south', 'tracking', ...... ] DATABASES = { 'default': { 'ENGINE': 'django.db.backends.postgresql_psycopg2', 'HOST': '127.0.0.1', 'NAME': 'xxxxxx', 'USER':

I want to call a plpgsql function through psycopg2 and see the warning messages. I.e, I have this function: create or replace function test_warning() returns void as $$ begin raise warning 'this is only a test'; end; $$ language plpgsql; and call it so in python: import psycopg2 conn = psycopg2.connect(conn_string) cursor = conn.cursor() cursor.callproc("test_warning") # or so: cursor.execute('SELECT test_warning()') Unfortunately the warning message as defined in plpgsql does not appear anywhere in the python output. Is there a way to get the warning message printed in the python output? The

What are the consequences of not closing a psycopg2 connection at the end of a Python script? For example, consider the following snippet: import psycopg2 psycopg2.connect("dbname=test") The script opens a connection, but does not close it at the end. Is the connection still open at the end of the execution? If so, is there an issue with not closing the connection? Normally when your python program exits, all the sockets it owns will be closed, and open transactions aborts. But it's good practice to close the connection at the very end. Closing a connection as soon as you don't need it anymore