https://projects.ecoinformatics.org/ecoinfo/https://projects.ecoinformatics.org/ecoinfo/ecoinfo/favicon.ico?14691340362003-12-12T00:27:28ZEcoinformatics RedmineMetacat - Bug #1238: postgresql JDBC config problem in metacathttps://projects.ecoinformatics.org/ecoinfo/issues/1238?journal_id=45632003-12-12T00:27:28ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>Interestingly, I have a current version of metacat running using the original<br />jdbc .jar file that is checked into lib. I have tested insert, update, and<br />delete operations through metacat using this jar without any problems. I have<br />the follwoing properties set in the build.properties:</p>
<ol>
<li>Select the database to use for metadata storage</li>
<li>Valid values are oracle, postgresql, sqlserver<br />database=postgresql</li>
</ol>
<ol>
<li>The JDBC connection string used to connect to the database<br />jdbc-connect=jdbc:postgresql://localhost/metacat</li>
</ol>
<ol>
<li>The base directory for locating JDBC jar files (not needed for postgresql)<br />jdbc_base=./lib</li>
</ol>
<p>It still might be a good idea to remove the jar file, but so far I have found it<br />convenient. The changes you suggest change the meaning of the 'jdbc-base" <br />property, which for other databases represents the directory in which the jdbc<br />jar file(s) can be found. If we were to change it, I would want to use the<br />properties consistently across the databases we support (oracle, postgres, mssql<br />server).</p>
<p>What did you try that did not work for you? Are you sure you ran postmaster<br />with -i and enabled tcp/ip access, and had the right jdbc connect string when<br />testing it? What OS was it failing on? Thanks for the further info.</p> Metacat - Bug #1238: postgresql JDBC config problem in metacathttps://projects.ecoinformatics.org/ecoinfo/issues/1238?journal_id=45642003-12-12T00:39:20ZDavid Kaplandmkaplan@ucdavis.edu
<ul></ul><p>What version of postgresql are you running? Generally, the drivers are forward<br />compatible as far as java is concerned - i.e. they will work with java-1.4 if<br />they work with 1.1. But I don't think the older driver will work with newer<br />versions of postgresql. It didn't appear to work for me, but then again I<br />didn't fuss much. In any case, perhaps the solution would be a new parameter<br />jdbc-jar that would only be used by postgresql.</p> Metacat - Bug #1238: postgresql JDBC config problem in metacathttps://projects.ecoinformatics.org/ecoinfo/issues/1238?journal_id=45652003-12-12T00:49:22ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>I am running postgresql 7.3, the most recent version for redhat 9 as of two days<br />ago. From what I can see the old jdbc jar file works fine with the new version<br />of postgres, but I agree we should look into this. One of the initial reasons<br />for checking it in was we were trying to make a standalone version of metacat<br />that had everything needed for it to run. We might have other ways of<br />accomplishing that now that we are closer to a binary installer capability.</p> Metacat - Bug #1238: postgresql JDBC config problem in metacathttps://projects.ecoinformatics.org/ecoinfo/issues/1238?journal_id=45662005-09-27T23:54:49ZMatt Jonesjones@nceas.ucsb.edu
<ul></ul><p>Upgraded the driver to the Postgresql version 8 JDBC driver. Tested against<br />postgres 7.4 and still seems to work. Marking as fixed for the 1.6 metacat release.</p> Metacat - Bug #1238: postgresql JDBC config problem in metacathttps://projects.ecoinformatics.org/ecoinfo/issues/1238?journal_id=45672013-03-27T21:16:36ZRedmine Admin
<ul></ul><p>Original Bugzilla ID was 1238</p>