Mailing-List: contact continuum-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: continuum-dev@maven.apache.org
Received-SPF: pass (herse.apache.org: domain of jesse.mcconnell@gmail.com
 designates 64.233.182.186 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=G6/tpJ2RG9zYpc5SNBMqTflRy1QP5YpwPH+vOpKQNhtO2N17Knu0kfArUt2c0V/wSiNpGqUMSWze9qFwPZj9SNDvPLw+gjQzNqMcniZMWTmOFmQsIsKcwCr5IbjozYMkYts8CchlOwLj0jt/9V3UR/mlvHTLBzRIwYP6vrUrsYs=
Message-ID: <a43524d00703141053o157514e5o5a8e68aedc7e9858@mail.gmail.com>
Date: Wed, 14 Mar 2007 12:53:48 -0500
From: "Jesse McConnell" <jesse.mcconnell@gmail.com>
To: continuum-dev@maven.apache.org
Subject: Re: JPOX 1.1.7 ?
In-Reply-To: <495914f00703140722n6a1c1786hf43813f5a5829b32@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <495914f00703131204j123d08fbt9efe5b5e9c1b2d7f@mail.gmail.com>
	 <a43524d00703131215q1080a70cx876058a1c0ff185b@mail.gmail.com>
	 <495914f00703131436s470fcd5bo6359a9680e8d0b2f@mail.gmail.com>
	 <a43524d00703131709m7d1a9113u61b13bee8ebc4d40@mail.gmail.com>
	 <495914f00703140644q25b58c47g4a7d1c663f66d043@mail.gmail.com>
	 <a43524d00703140705k61e91f45w4eca404604a900b5@mail.gmail.com>
	 <495914f00703140722n6a1c1786hf43813f5a5829b32@mail.gmail.com>

I am getting issues with starting continuum with the jpox 1.1.7 and
postgres myself

different stacks though

g: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
"PROJECTGROUP_BUILDDEFINITIONS_pkey" for table
"PROJECTGROUP_BUILDDEFINITIONS"
2007-03-14 12:48:37,539 [main] WARN  General                        -
SQL warning: NOTICE: CREATE TABLE / PRIMARY KEY will create implicit
index "PROJECTNOTIFIER_CONFIGURATION_pkey" for table
"PROJECTNOTIFIER_CONFIGURATION"
2007-03-14 12:48:37,676 [main] ERROR Schema                         -
An exception was thrown while adding/validating class(es) : ERROR:
function information_schema._pg_keypositions() does not exist
java.sql.SQLException: ERROR: function
information_schema._pg_keypositions() does not exist
        at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1471)
        at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1256)
        at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:175)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:389)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:314)
        at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:221)
        at org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedExportedKeys(AbstractJdbc2DatabaseMetaData.java:3237)
        at org.postgresql.jdbc2.AbstractJdbc2DatabaseMetaData.getImportedKeys(AbstractJdbc2DatabaseMetaData.java:3533)
        at org.jpox.store.rdbms.RDBMSStoreHelper.getForeignKeyInfoForTable(RDBMSStoreHelper.java:376)
        at org.jpox.store.rdbms.table.TableImpl.getExistingForeignKeys(TableImpl.java:937)
        at org.jpox.store.rdbms.table.TableImpl.validateForeignKeys(TableImpl.java:421)
        at org.jpox.store.rdbms.table.TableImpl.validateConstraints(TableImpl.java:394)
        at org.jpox.store.rdbms.table.ClassTable.validateConstraints(ClassTable.java:2875)
        at org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(RDBMSManager.java:3110)

On 3/14/07, Thierry Lach <thierry.lach@gmail.com> wrote:
> Yeah, that was my thought also.
>
> On 3/14/07, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:
> >
> > have you tried it with postgres outside of jboss?  I want to narrow
> > down the factors here
> >
> >
> >
> > On 3/14/07, Thierry Lach <thierry.lach@gmail.com> wrote:
> > > That's right. I knew that patch for transaction levels didn't solve it
> > on
> > > its own, so my hopes got up with the mention of JPOX 1.1.7 and postgres
> > last
> > > week.
> > >
> > > On 3/13/07, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:
> > > >
> > > > I set the transaction lvls to READ_COMMITTED as well, so that didn't
> > > > fix you either huh?
> > > >
> > > > hrm
> > > >
> > > > On 3/13/07, Thierry Lach <thierry.lach@gmail.com> wrote:
> > > > > JPOX 1.1.7 doesn't correct the problems with Postgres.  I've added
> > an
> > > > > updated stack trace to
> > http://jira.codehaus.org/browse/CONTINUUM-1181
> > > > >
> > > > > On 3/13/07, Jesse McConnell <jesse.mcconnell@gmail.com> wrote:
> > > > > >
> > > > > > yes, and I setup the bundled for m2 and got them into place about
> > an
> > > > > > hour ago...will be synced into the main repos sometime soon
> > > > > >
> > > > > > jesse
> > > > > >
> > > > > > On 3/13/07, Thierry Lach <thierry.lach@gmail.com> wrote:
> > > > > > > Did JPOX 1.1.7 get released yesterday?
> > > > > > >
> > > > > > > On 3/7/07, Erik Bengtson <erik@jpox.org> wrote:
> > > > > > > >
> > > > > > > > FYI, JPOX 1.1.7 will be released next monday. It fixes the
> > issue
> > > > with
> > > > > > > > postgres.
> > > > > > > >
> > > > > > > > You can try it out, if you like, before we release.
> > > > > > > >
> > > > > > > >
> > > > http://www.jpox.org/downloads/maven/jpox/jars/jpox-1.1-SNAPSHOT.jar
> > > > > > > >
> > > > > > > > Regards
> > > > > > > >
> > > > > > > > Quoting Jesse McConnell <jesse.mcconnell@gmail.com>:
> > > > > > > >
> > > > > > > > > Ok, well the little poll thread I made seemed to be strongly
> > in
> > > > > > favor
> > > > > > > > > of getting things pulled together to start getting alpha
> > > > releases
> > > > > > out
> > > > > > > > > of continuum.  So with that in mind here is a list of a few
> > > > things
> > > > > > > > > that we need to get in order for an alpha release that I
> > > > shamelessly
> > > > > > > > > started base on bretts comments
> > > > > > > > >
> > > > > > > > > - properly mark up the model as it was for 1.0.3 release
> > > > > > > > > - add methods to continuum-data-management to utilise that
> > and
> > > > then
> > > > > > > > > make any necessary transformations (c-d-m will do the basic
> > > > 1-to-1
> > > > > > > > > conversions)
> > > > > > > > > - probably write a little CLI to fire it off.
> > > > > > > > > - vet jira for a 1.1 alpha 1 release version and maybe
> > schedule
> > > > out
> > > > > > a
> > > > > > > > > couple of alpha-# releases.
> > > > > > > > >
> > > > > > > > > I think I'll start in on the data management bit now since
> > that
> > > > > > seems
> > > > > > > > > like the biggest hurdle.  I am not convinced we really need
> > to
> > > > worry
> > > > > > > > > about a continuum 1.0.3 -> continuum 1.1 migration
> > ability...its
> > > > not
> > > > > > a
> > > > > > > > > difficult thing to get projects loaded back up into
> > > > continuum...but
> > > > > > > > > we'll see I guess.
> > > > > > > > >
> > > > > > > > > anyone have anything to add?
> > > > > > > > >
> > > > > > > > > jesse
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > jesse mcconnell
> > > > > > > > > jesse.mcconnell@gmail.com
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > jesse mcconnell
> > > > > > jesse.mcconnell@gmail.com
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > jesse mcconnell
> > > > jesse.mcconnell@gmail.com
> > > >
> > >
> >
> >
> > --
> > jesse mcconnell
> > jesse.mcconnell@gmail.com
> >
>


-- 
jesse mcconnell
jesse.mcconnell@gmail.com