value to large for column errors?

[Michael Harris <mi...@gmail.com>]

Anyone seen and know how to resolve value too large for column errors like

value too large for column "schema"."DEFAULT_BINVAL"."BINVAL_ID"
(actual: 72, maximum: 64)

(I replaced the schema value with schema)

whats wierd is I can run my tests locally but when the automated environment
tries to run the tests I get those errors.

i also see

 unique constraint (schema.DEFAULT_PROP_IDX) violated



again replacing my schema name with schema

thanx

-- 
---------------------
Michael Harris

Re: value to large for column errors?

[Michael Harris <mi...@gmail.com>]

i think it was bad configuration -- i have the automated script drop the
repo.home dir (and recreate it) and the tests run just fine.

I know Ive asked a lot about what data is managed on the disk, and what the
distinction between FS and PM is, but given that I can delete my repo.home
and fire up TransientRepo instances and have it work Im a bit confused.   My
test environment uses the spring-modules jcr support so all my tests are
wrapped in a transaction (one tx per test) so the data goes away at the end
of each test, which might be why Im not having issues with deleting
repo.home.  I am also have all FS as db file systems, which will have to
change because we cannot have a db user used by the app that can
create/delete tables....

O  Wed, Aug 13, 2008 at 5:20 AM, Stefan Guggisberg <
stefan.guggisberg@day.com> wrote:

> On Tue, Aug 12, 2008 at 5:44 PM, Michael Harris
> <mi...@gmail.com> wrote:
> > Anyone seen and know how to resolve value too large for column errors
> like
> >
> > value too large for column "schema"."DEFAULT_BINVAL"."BINVAL_ID"
> > (actual: 72, maximum: 64)
>
> that's most likely caused by incorrect table creation. did you create
> them manually?
>
> >
> > (I replaced the schema value with schema)
> >
> > whats wierd is I can run my tests locally but when the automated
> environment
> > tries to run the tests I get those errors.
> >
> > i also see
> >
> >  unique constraint (schema.DEFAULT_PROP_IDX) violated
>
> you're probably having more than 1 jackrabbit instance accessing the same
> db/schema...
>
> cheers
> stefan
>
> >
> >
> >
> > again replacing my schema name with schema
> >
> > thanx
> >
> > --
> > ---------------------
> > Michael Harris
> >
>



-- 
---------------------
Michael Harris

Re: value to large for column errors?

[Stefan Guggisberg <st...@day.com>]

On Tue, Aug 12, 2008 at 5:44 PM, Michael Harris
<mi...@gmail.com> wrote:
> Anyone seen and know how to resolve value too large for column errors like
>
> value too large for column "schema"."DEFAULT_BINVAL"."BINVAL_ID"
> (actual: 72, maximum: 64)

that's most likely caused by incorrect table creation. did you create
them manually?

>
> (I replaced the schema value with schema)
>
> whats wierd is I can run my tests locally but when the automated environment
> tries to run the tests I get those errors.
>
> i also see
>
>  unique constraint (schema.DEFAULT_PROP_IDX) violated

you're probably having more than 1 jackrabbit instance accessing the same
db/schema...

cheers
stefan

>
>
>
> again replacing my schema name with schema
>
> thanx
>
> --
> ---------------------
> Michael Harris
>