easy resetting - Search results in mailing lists
Mailing lists >> pgsql-interfaces >> Thread
2008-03-23 15:14:20 | Re: ECPG connection timeouts (meskes@postgresql.org)
easy, but apparently PQsetdbLogin does not really set the option correctly. Before looking for the bug which might be a formatting problem in ecpg but appears to be a PQsetdbLogin limitation I think I better
Mailing lists >> pgsql-interfaces >> Thread
2003-04-21 22:30:40 | Re: DBD::Pg large processor load. (Chris Gamache)
setting, to tone down DBI's (perceived) voracity for processor time! PgSQL::Cursor was alpha software when I started using it. It was simple to impliment, and did the trick. It was eclipsed
Mailing lists >> pgsql-interfaces >> Thread
2003-02-12 20:30:32 | Re: Prepare and prepare ? (David Wheeler)
easier, but I don't know if anything has been done. But I was under the assumption that if you used "text" for the data types that they would be cast without too much trouble
Mailing lists >> pgsql-interfaces >> Thread
2001-04-16 17:25:35 | Re: backend debug information (Tom Lane)
Setting breakpoints in dynamically loaded shared libraries (ie, user datatype code) may be easy, painful
Mailing lists >> pgsql-interfaces >> Thread
2001-01-15 05:05:37 | pgAdmin v7.0.5 Released (Dave Page)
setting of Privileges on Sequences in the Privilege dialogue. - Fixed the code in the Add Column dialogue which failed to set NOT NULL and DEFAULT ??? due to syntax problems. - Removed old 'Open Maximised' code which
Mailing lists >> pgsql-interfaces >> Thread
2000-12-20 13:16:30 | Re: [ADMIN] Help me for "DBI->connect failed: Sorry, too many clients already." (Jie Liang)
setting according to the doccument. open too many sessiones at same time will more or less affect the performance. 2. I believe that using Pg module will be easier
Mailing lists >> pgsql-interfaces >> Thread
2000-11-30 16:05:47 | Some advice re:bound/unbound forms for MS Access (Joel Burton)
settings are correct so that ODBC lets you update and insert records w/o the #Deleted problems and such. See the PostgreSQL + Access FAQ (described below) if you need help. 1) Create a normal, bound form
Mailing lists >> pgsql-interfaces >> Thread
2000-07-26 14:33:34 | Access + Microsoft Access FAQ (Long) (Joel Burton)
settings in the ODBC driver? . What field types work well in Access? . How can I reconcile the limit of Access Memo types (~2 billion chars) w/the limit of PostgreSQL Text types (~8k)? . What considerations should
Mailing lists >> pgsql-interfaces >> Thread
2000-06-19 15:24:23 | Simple Q: Does the ODBC driver support LONGVARCHAR? (Adam Rossi)
settings for the driver, such as checking "Unknowns as LongVarChar", "Text as LongVarChar", "Parse Statements", etc., the longvarchar type NEVER works. In this simple SQL statement: create table test_table testid INTEGER,text_field LONGVARCHAR
Mailing lists >> pgsql-interfaces >> Thread
1999-12-16 11:29:55 | Database replication under Postgres (Paul Breen)
setting up rules on a table to NOTIFY me of an insert|update|delete and then have a program that queries the difference between the two databases and synchronises them accordingly. This
Mailing lists >> pgsql-interfaces >> Thread
1999-12-16 09:34:55 | Database replication under Postgres (Paul Breen)
setting up rules on a table to NOTIFY me of an insert|update|delete and then have a program that queries the difference between the two databases and synchronises them accordingly. This
Mailing lists >> pgsql-interfaces >> Thread
1999-10-01 15:55:46 | Problems with large objects and 6.51 (Wolfgang Hottgenroth)
easy to handle it as part of the main * loop. Save the data and continue processing. */ if (pqGetInt(&(conn->be_pid), 4, conn)) return; if (pqGetInt(&(conn->be_key), 4, conn)) return; break; case
Mailing lists >> pgsql-interfaces >> Thread
1999-08-27 13:20:42 | problems with large objects (Wolfgang Hottgenroth)
easy to handle it as part of the main * loop. Save the data and continue processing. */ if (pqGetInt(&(conn->be_pid), 4, conn)) return; if (pqGetInt(&(conn->be_key), 4, conn)) return; break; case
Mailing lists >> pgsql-interfaces >> Thread
1999-07-08 23:24:49 | Undeliverable Message ()
settings to cope with a different object format. This is a problem that is generally not experienced under UNIX, because there is only one object format (that I'm aware of). I'm not sure
Mailing lists >> pgsql-interfaces >> Thread
1999-03-25 02:00:43 | Undeliverable Message ()
settings translation_dllconn&282108, SQLDriverConnect(out)Global Options: Version disable_optimizer _index_declarefetch text_as_longvarchars_longvarchar ools_as_char extra_systable_prefixesconn&282108, queryconn&282108, queryconn&282108, queryconn&282108, query [ fetched 0 rows