PDA

View Full Version : pgsql Interfaces odbc

Pages : 1 2 3 4 5 6 [7] 8 9 10
  1. unsubscribe
  2. Re: [PATCH] initialize pgconn to null
  3. Re: EN_Destructor bug?
  4. Re: ODBC driver and linked server in MSSQL 2k
  5. EN_Destructor bug?
  6. [PATCH] initialize pgconn to null
  7. Re: versions of oDBC driver
  8. Re: MAC OSX copy_and_convert_field bug for SQL_W_CHAR
  9. Migracion de BD SQL Server 2000 a PostgreSQL
  10. Problema con mi BD
  11. Re: MAC OSX copy_and_convert_field bug for SQL_W_CHAR
  12. MAC OSX copy_and_convert_field bug for SQL_W_CHAR
  13. Re: versions of oDBC driver
  14. unixODBC vs postgeSQL driver on RHEL4?
  15. vb6 inquiry
  16. Problems compiling odbc
  17. Anyway to get "official" odbc rpms?
  18. Re: select a non numeric fields problem
  19. Re: select a non numeric fields problem
  20. Re: select a non numeric fields problem
  21. select a non numeric fields problem
  22. select in non numeric fields problem
  23. select a non numeric fields problem
  24. Re: Odbc Problem
  25. Odbc Problem
  26. Re: how to compile psqlodbc.dll on windows?
  27. how to compile psqlodbc.dll on windows?
  28. Re: Problem with psqlODBC on "Cache Size"
  29. Re: Problem with psqlODBC on "Cache Size"
  30. Re: lock - feedback
  31. Re: lock - feedback
  32. Re: lock - feedback
  33. Re: lock - feedback
  34. Re: lock - feedback
  35. Re: installer
  36. Re: installer
  37. lock - feedback
  38. Re: Using pg_config
  39. Re: universal path
  40. Re: Fix permissions in CVS repository
  41. Fix permissions in CVS repository
  42. Re: Using pg_config
  43. Using pg_config
  44. Remove Debian Howto
  45. Re: QUERY : RE: Four art Names
  46. Re: Problem with psqlODBC on "Cache Size"
  47. Re: Windows, ODBC drivers and strange points ...
  48. Problem with psqlODBC on "Cache Size"
  49. Re: Windows, ODBC drivers and strange points ...
  50. Windows, ODBC drivers and strange points ...
  51. Re: app crashes if lost connection during query, seems to be a bug.
  52. app crashes if lost connection during query, seems to be a bug.
  53. (NONE)
  54. Re: cursor control
  55. Re: CVS Moved
  56. Re: QUERY : RE: Four art Names
  57. QUERY : RE: Four art Names
  58. unsubscribe
  59. Re: Insecurity of ODBC debug logging files
  60. Re: Just as an FYI We are up solid now on pgsql libpq version
  61. Insecurity of ODBC debug logging files
  62. Re: Just as an FYI We are up solid now on pgsql libpq version
  63. Just as an FYI We are up solid now on pgsql libpq version
  64. Re: PATCH: Integrity constraint violation should set SQLSTATE to 23000
  65. Re: Unbound text box, Text > 255 characters, MSAccess/PostgreSQL
  66. Get error message details
  67. ODBC driver Feature request
  68. Re: Integrity constraint violation should set SQLSTATE to 23000
  69. Integrity constraint violation should set SQLSTATE to 23000
  70. select count(*) datatype ?
  71. Re: PostgreSQL / ODBC / Ms-SQL 2000
  72. Re: PostgreSQL / ODBC / Ms-SQL 2000
  73. Re: Problems with PsqlOdbc.
  74. Re: ODBC driver types
  75. Problems with PsqlOdbc.
  76. Re: Compiling with libpq
  77. Re: PostgreSQL / ODBC / Ms-SQL 2000
  78. Re: Problem with Cursor in Oracle from Postgresql via ODBC
  79. Problem with Cursor in Oracle from Postgresql via ODBC
  80. Re: PostgreSQL / ODBC / Ms-SQL 2000
  81. Re: PostgreSQL / ODBC / Ms-SQL 2000
  82. postgresql-odbc vs. unixODBC
  83. Re: unsubscribe
  84. unsubscribe
  85. unsubscribe
  86. 86 come and get me boys 86
  87. Driver uninstall bug ?
  88. Re: A Question on SQL_C_NUMERIC
  89. A Question on SQL_C_NUMERIC
  90. Re: client encoding mismatch
  91. Connecting to postgreSQL
  92. Re: client encoding mismatch
  93. Re: ODBC driver types
  94. ODBC driver types
  95. Re: Access end Postgres
  96. Access end Postgres
  97. Re: client encoding mismatch
  98. Re: Changing a database
  99. Changing a database
  100. Re: We have to support ANSI encoding...
  101. We have to support ANSI encoding...
  102. Re: client encoding mismatch
  103. client encoding mismatch
  104. Problema with Varchar on version 8x of ODBC Driver
  105. Re: [PATCH] notice handler
  106. Re: [PATCH] notice handler
  107. Re: [PATCH] notice handler
  108. Re: [PATCH] notice handler
  109. Re: [PATCH] fix for wrong error code returned
  110. [PATCH] notice handler
  111. [PATCH] fix for wrong error code returned
  112. client encoding mismatch
  113. Re: row count with libpq driver
  114. Re: row count with libpq driver
  115. Re: row count with libpq driver
  116. Re: ODBC Driver on Windows 64 bit
  117. Re: changed behavior in libpq odbc driver
  118. WORKAROUND SOLUTION INFO & PLEASE PROVIDE A 32 BIT CONFIGURE OPTION
  119. Re: ODBC Driver on Windows 64 bit
  120. Re: ODBC Driver on Windows 64 bit
  121. Re: ODBC Driver on Windows 64 bit
  122. Re: row count with libpq driver
  123. Re: PATCH: SQLTables and case sensitivity
  124. Re: PATCH: SQLTables and case sensitivity
  125. Re: PATCH: SQLTables and case sensitivity
  126. Re: SQLTables and case sensitivity
  127. SQLTables and case sensitivity
  128. Re: ODBC Driver on Windows 64 bit
  129. Re: ODBC Driver on Windows 64 bit
  130. Re: problem
  131. Connecting from ORACLE to PostgreSQL via ODBC does not work: "driver not licensed"
  132. odbc support in PostgreSQL 8.0.3
  133. Re: Frontend/Backend protocol 3.0 update
  134. Client encoding mismatch
  135. problem
  136. Frontend/Backend protocol 3.0 update
  137. Regarding Mutiple cursor returning in PostGres
  138. Re: row count with libpq driver
  139. row count with libpq driver
  140. Re: ODBC Driver on Windows 64 bit
  141. Re: ODBC Driver Failure- MS Access- Large record volume
  142. Re: ODBC Driver Failure- MS Access- Large record volume
  143. ODBC Driver Failure- MS Access- Large record volume
  144. ODBC Driver on Windows 64 bit
  145. Re: Application bottlenecks
  146. Re: Application bottlenecks
  147. Re: Application bottlenecks
  148. Re: Continuing encoding fun....
  149. Re: Continuing encoding fun....
  150. Re: changed behavior in libpq odbc driver
  151. Re: changed behavior in libpq odbc driver
  152. lo type and ODBC
  153. Re: notice handler in libpq-based driver
  154. Re: changed behavior in libpq odbc driver
  155. Re: changed behavior in libpq odbc driver
  156. Re: changed behavior in libpq odbc driver
  157. Re: changed behavior in libpq odbc driver
  158. Application bottlenecks
  159. Re: notice handler in libpq-based driver
  160. Re: Critical Bug with UseDeclareFetch in development version
  161. Re: Using Which Driver [correct]
  162. Re: changed behavior in libpq odbc driver
  163. Re: changed behavior in libpq odbc driver
  164. notice handler in libpq-based driver
  165. Re: Migration from odbc driver 7.x to 8.x
  166. Migration from odbc driver 7.x to 8.x
  167. Re: Continuing encoding fun....
  168. Re: Continuing encoding fun....
  169. Re: Continuing encoding fun....
  170. Re: Using Which Driver [correct]
  171. Re: Continuing encoding fun....
  172. Re: Using Which Driver [correct]
  173. Re: Continuing encoding fun....
  174. Re: Unicode support
  175. Re: Unicode support
  176. Distributed Transaction
  177. why is TextAsLongVarchar=1 per default?
  178. Re: Continuing encoding fun....
  179. Re: Continuing encoding fun....
  180. Re: Continuing encoding fun....
  181. last question.. sorry
  182. Re: savepoint
  183. limit & offset
  184. Continuing encoding fun....
  185. Re: savepoint
  186. Re: Unicode support, first test results
  187. c++ mfc: problem with bytea
  188. Re: figuring out why I am having this issue
  189. Re: crash in LIBPQ_execute_query
  190. Re: crash in LIBPQ_execute_query
  191. Re: figuring out why I am having this issue
  192. Re: crash in LIBPQ_execute_query
  193. crash in LIBPQ_execute_query
  194. Re: Unicode support
  195. Re: Unicode support
  196. ERROR AL CONECTAR VIA ODBC A FOXPRO
  197. Re: figuring out why I am having this issue
  198. Re: figuring out why I am having this issue
  199. Re: figuring out why I am having this issue
  200. Re: figuring out why I am having this issue
  201. Re: figuring out why I am having this issue
  202. Re: figuring out why I am having this issue
  203. Re: figuring out why I am having this issue
  204. Re: Unicode support
  205. Re: Unicode support
  206. Re: Unicode support
  207. CVS Moved
  208. Re: figuring out why I am having this issue
  209. Re: figuring out why I am having this issue
  210. figuring out why I am having this issue
  211. Re: Unicode support
  212. Re: changed behavior in libpq odbc driver
  213. E_Failed issue (also problem reading the record to edit it).
  214. Re: changed behavior in libpq odbc driver
  215. Re: changed behavior in libpq odbc driver
  216. Re: changed behavior in libpq odbc driver
  217. Re: changed behavior in libpq odbc driver
  218. Re: Transactions and SavePoints
  219. Re: changed behavior in libpq odbc driver
  220. Re: Unicode support
  221. Re: Unicode support
  222. Re: changed behavior in libpq odbc driver
  223. [Fwd: Re: Transactions and SavePoints]
  224. Unicode support
  225. Transactions and SavePoints
  226. Re: changed behavior in libpq odbc driver
  227. connections running out
  228. Re: changed behavior in libpq odbc driver
  229. psqlodbc 3.5x compliance gap analysis report
  230. Re: changed behavior in libpq odbc driver
  231. Re: changed behavior in libpq odbc driver
  232. Using Which Driver
  233. message dupes anyone ?
  234. conectividad postgresql con access
  235. Re: Four part names
  236. Four part names
  237. SQL query with no result set but inserting possible ?
  238. Re: Unexpected ADO properties
  239. Congratz
  240. Re: Conexion posgresql con Oracle
  241. bool tanformed into char
  242. Re: Unexpected ADO properties
  243. Re: changed behavior in libpq odbc driver
  244. Re: changed behavior in libpq odbc driver
  245. Trouble with encoding again
  246. Re: "Official" version
  247. Re: changed behavior in libpq odbc driver
  248. Re: ODBC Problem
  249. Re: ODBC driver: Rows Affected
  250. Re: ODBC driver: Rows Affected