PDA

View Full Version : pgsql Interfaces odbc

Pages : 1 2 3 4 5 6 7 [8] 9 10
  1. conectividad postgresql con access
  2. Re: Four part names
  3. Four part names
  4. SQL query with no result set but inserting possible ?
  5. Re: Unexpected ADO properties
  6. Congratz
  7. Re: Conexion posgresql con Oracle
  8. bool tanformed into char
  9. Re: Unexpected ADO properties
  10. Re: changed behavior in libpq odbc driver
  11. Re: changed behavior in libpq odbc driver
  12. Trouble with encoding again
  13. Re: "Official" version
  14. Re: changed behavior in libpq odbc driver
  15. Re: ODBC Problem
  16. Re: ODBC driver: Rows Affected
  17. Re: ODBC driver: Rows Affected
  18. Re: changed behavior in libpq odbc driver
  19. ODBC driver: Rows Affected
  20. SQLDescribeParam not defined: any workaround?
  21. Re: "Official" version
  22. Re: "Official" version
  23. Bug in SQLConnect, psqlodbc 08.00.00.04
  24. Re: "Official" version
  25. Re: "Official" version
  26. Re: changed behavior in libpq odbc driver
  27. ODBC Call Failed on Subform
  28. Unexpected ADO properties
  29. Re: "Official" version
  30. Re: "Official" version
  31. Re: "Official" version
  32. Re: "Official" version
  33. Re: "Official" version
  34. MS Access 2000 w/ PGSQL 8.0.x
  35. Re: "Official" version
  36. "Official" version
  37. Re: Bug or not about ASCII and Multi-Byte character set
  38. Re: Bug or not about ASCII and Multi-Byte character set
  39. Re: changed behavior in libpq odbc driver
  40. dates and selection
  41. Re: Conexion posgresql con Oracle
  42. Re: changed behavior in libpq odbc driver
  43. Conexion posgresql con Oracle
  44. Re: changed behavior in libpq odbc driver
  45. changed behavior in libpq odbc driver
  46. Using psqlodbc.dll without installing or registering
  47. Re: latest odbc in production status report.
  48. Re: Implementing IPv6 ...
  49. Re: Implementing IPv6 ...
  50. Re: New libpq based driver snapshot 08.01.0003 available
  51. =?gb2312?B?cmU6cHNxbG9kYmMtMDhfMDBfMDEwMiBhbmQgTEF USU4xIGRhdGFiYXM=?==?gb2312?B?ZSA=?=
  52. Re: Bug or not about ASCII and Multi-Byte character set
  53. ODBC Problem
  54. psqlodbc-08_00_0102 and LATIN1 database
  55. 'Key violation' error
  56. Re: Bug or not about ASCII and Multi-Byte character set
  57. Bug or not about ASCII and Multi-Byte character set
  58. Re: Libpq driver: thread problem
  59. latest odbc in production status report.
  60. Re: Libpq driver: thread problem
  61. Re: Libpq driver: thread problem
  62. Re: Libpq driver: thread problem
  63. Re: Implementing IPv6 ...
  64. Re: libpq odbc and OS X
  65. Re: psqlODBC 08.00.0102 available for download
  66. Re: New libpq driver snapshot
  67. libpq odbc and OS X
  68. Re: psqlODBC 08.00.0102 available for download
  69. HELP: Unrecognized key passed to SQLGetInfo30(#209)
  70. troubles with configure script on solaris ...
  71. Re: psqlODBC 08.00.0102 available for download
  72. Re: Updates to page on using psqlodbc with Debian
  73. Re: psqlODBC 08.00.0102 available for download
  74. Re: [ADMIN] PG 7.3.4 VS PG 8.0.3 Problem
  75. Re: psqlodbclibpq 8_1_03 unicode problem
  76. Re: psqlodbclibpq 8_1_03 unicode problem
  77. Re: [ADMIN] PG 7.3.4 VS PG 8.0.3 Problem
  78. Re: psqlodbclibpq 8_1_03 unicode problem
  79. Re: psqlodbclibpq 8_1_03 unicode problem
  80. Re: Updates to page on using psqlodbc with Debian
  81. psqlodbclibpq 8_1_03 unicode problem
  82. Re: [ADMIN] PG 7.3.4 VS PG 8.0.3 Problem
  83. Re: [ADMIN] PG 7.3.4 VS PG 8.0.3 Problem
  84. Re: postgresqlodbc ssl connections
  85. Re: postgresqlodbc ssl connections
  86. Re: issue using dts and odbc driver with unicode
  87. Re: ODBC driver and linked server in MSSQL 2k
  88. postgresqlodbc ssl connections
  89. ODBC driver and linked server in MSSQL 2k
  90. issue using dts and odbc driver with unicode
  91. Re: Remopte connection to POstgreSQL via ODBC
  92. SQLFreeStmt problem ?
  93. Remopte connection to POstgreSQL via ODBC
  94. Unsubscribe
  95. Re: error during build, I must of hosed something
  96. error during build, I must of hosed something
  97. Re: UICODE SUPPORT IN 8.00.0102
  98. Re: Use Declare/Fetch in new version
  99. Re: Usind database with encoding UNICODE and vovel
  100. Re: SQLColAttribute and SQL_DESC_BASE_TABLE_NAME
  101. Re: Usind database with encoding UNICODE and vovel
  102. Re: Usind database with encoding UNICODE and vovel
  103. Re: Usind database with encoding UNICODE and vovel
  104. Re: Usind database with encoding UNICODE and vovel
  105. Re: Usind database with encoding UNICODE and vovel
  106. Re: New libpq driver snapshot
  107. Re: Bug in libpq version - solved
  108. Re: Usind database with encoding UNICODE and vovel
  109. Re: Usind database with encoding UNICODE and vovel
  110. Re: New libpq based driver snapshot 08.01.0003 available
  111. unsubscribe
  112. iODBC vs unixODBC (which to use)
  113. New libpq based driver snapshot 08.01.0003 available
  114. Re: Usind database with encoding UNICODE and vovel
  115. Re: psqlODBC 08.00.0102 available for download
  116. Re: Usind database with encoding UNICODE and vovel
  117. Re: psqlODBC 08.00.0102 available for download
  118. Re: Bug in libpq version
  119. Re: psqlODBC 08.00.0102 available for download
  120. Bug in libpq version
  121. Re: psqlODBC 08.00.0102 available for download
  122. Re: psqlODBC 08.00.0102 available for download
  123. Re: IIS Postgres ASP ADO - Problem
  124. psqlODBC 08.00.0102 available for download
  125. Re: Libpq free bug? (Was: IIS Postgres ASP ADO - Problem)
  126. Re: IIS Postgres ASP ADO - Problem
  127. Re: [BUGS] problem odbc 8.0 with EOModeler
  128. Re: Lowercase folding - simple patch?
  129. Re: undefined symbol: ucs2_to_utf8
  130. undefined symbol: ucs2_to_utf8
  131. Re: IIS Postgres ASP ADO - Problem
  132. SQLPrimaryKeys on Mac OS X 10.3 failed ??
  133. problem odbc 8.0 with EOModeler
  134. A6 parameter in ODBC connection string
  135. Re: psqlodbc CVS source code FAIL compile (libpq-fe.h)
  136. odbc win.xp and mandrake 10
  137. Re: Lowercase folding - simple patch?
  138. iODBC & Mac OS
  139. Re: Ok... I got most of it working but . . .
  140. Re: Lowercase folding - simple patch?
  141. Lowercase folding - simple patch?
  142. Ok... I got most of it working but . . .
  143. Re: still no luck with excel
  144. Re: still no luck with excel
  145. Re: still no luck with excel
  146. Re: Illegal access violation
  147. still no luck with excel
  148. Re: Illegal access violation
  149. Illegal access violation
  150. Re: WHat do people think about using in production?
  151. Re: WHat do people think about using in production?
  152. Re: MS Access & foreign encoding bug
  153. Re: MS Access & foreign encoding bug
  154. Re: [Patch] SSL Support
  155. Re: [Patch] SSL Support
  156. WHat do people think about using in production?
  157. Re: ODBC Driver
  158. MS Access & foreign encoding bug
  159. Re: [Patch] SSL Support
  160. ODBC Driver
  161. Connection Pooling
  162. Row versionning between MS-Access and PostgreSQL 8
  163. Re: Static analysis run
  164. Row versionning between MS-Access and PostgreSQL 8
  165. Re: Static analysis run
  166. Static analysis run
  167. Re: MaxLongVarcharSize=8190;
  168. Re: New libpq driver snapshot
  169. Re: psqlodbc CVS source code FAIL compile (libpq-fe.h)
  170. psqlodbc CVS source code FAIL compile (libpq-fe.h)
  171. New libpq driver snapshot
  172. Re: Blank varchar and text fields
  173. Re: MaxLongVarcharSize=8190;
  174. MaxLongVarcharSize=8190;
  175. Blank varchar and text fields
  176. Re: debug=1 supposed to be working? Any clue where I should look to see why I always get a catastrophic error when I enable it?
  177. Re: what is best way to get the latest libpq version.
  178. Re: what is best way to get the latest libpq version.
  179. Re: what is best way to get the latest libpq version.
  180. what is best way to get the latest libpq version.
  181. Best way of retrieving tablename from a query ?
  182. Re: psqlodbc libpq version: quiet error on connect failure
  183. Re: psqlodbc libpq version: quiet error on connect failure
  184. A correction into the connect exit(1) problem
  185. psqlodbc libpq version: quiet error on connect failure
  186. Re: Leak repairs
  187. Re: Leak repairs
  188. Re: Leak repairs
  189. Re: Leak repairs
  190. Re: Leak repairs
  191. bad day for Unicode
  192. psqlodbc-08_00_0101 does not work with Ms Access
  193. Re: Leak repairs
  194. Best way of retrieving tablename from a query ?
  195. MFC issues with ODBC
  196. How to get the number of rows deleted
  197. Re: Fix for the 'null value' bug
  198. Fix for the 'null value' bug
  199. Has anyone accessed postgresql in linux from VB code
  200. Help needed
  201. IS it a BUG !?
  202. IS it a BUG !?
  203. Re: Libpq driver: thread problem
  204. Re: Libpq driver: thread problem
  205. Re: Libpq driver: thread problem
  206. Libpq based driver available for testing
  207. Benchmark results
  208. Re: pgsql-odbc
  209. Re: I tried turning on debug in a dsn less connection and get Catastrophic failure?
  210. Re: Error Report on ODBC Connect Dialog
  211. Re: libpq odbc: unrecognized return value from copy_and_convert_field
  212. using cursors?
  213. I tried turning on debug in a dsn less connection and getCatastrophic failure?
  214. Re: Specified driver could not be loaded due to system error 998 (PostgreSQL).
  215. Specified driver could not be loaded due to system error 998(PostgreSQL).
  216. Libpq based driver
  217. Re: Patch for Libpq enabled psqlodbc
  218. Unsubscribe
  219. Re: Patch for Libpq enabled psqlodbc
  220. Re: Patch for Libpq enabled psqlodbc
  221. Re: Patch for Libpq enabled psqlodbc
  222. pgsql-odbc
  223. Re: Patch for Libpq enabled psqlodbc
  224. MS Access and #deleted due to timeouts
  225. Re: Patch for Libpq enabled psqlodbc
  226. Re: libpq enabled psqlodbc
  227. Re: libpq enabled psqlodbc
  228. connx odbc driver
  229. Error Report on ODBC Connect Dialog
  230. Problems with ODBC and ASP .NET 2.0
  231. iodbc x unixodbc
  232. hello
  233. get the SALT
  234. Re: delphi access question?
  235. Re: [ADMIN] encoding converting from ascii to unicode (I got it
  236. What to do about errors returned by odbc
  237. Re: libpq enabled psqlodbc
  238. Re: Patch for cursor type fallback
  239. ODBC connection on Win
  240. libpq enabled psqlodbc
  241. psqlodbc compile problem on Solaris 9
  242. Patch for cursor type fallback
  243. rollback to savepoint support
  244. Some additions to odbc codepage problem
  245. how to disable connection pooling?
  246. Re: {? = call myfunc(?,?)} syntax for set-returning functions
  247. can't open more than 128 connections
  248. Re: Can I specify a SCHEMA in the ODBC string?
  249. Edit postgre database in Visual Studio 2003
  250. Re: Set timezone in ODBC