Did anybody get RC2 fully working on PGSQL 7.3x?

Author Message

Christoph Nelles

Thursday 06 February 2003 3:58:30 pm

At my site, it always crashs and complains about missing objects in the admin interface. does anybody have made the same experience? or has some pgsql user it fully running?

Bård Farstad

Friday 07 February 2003 12:21:20 am

> At my site, it always crashs and complains about missing
> objects in the admin interface. does anybody have made the
> same experience? or has some pgsql user it fully running?

I'm running eZ publish on PostgreSQL 7.2.1 test server here. I will upgrade to 7.3 and verify that everything is working there as well.

--bård

Documentation: http://ez.no/doc

Christoph Nelles

Friday 07 February 2003 3:48:45 am

I found the error! it occurs if you use the german translation files from RC1.

> I'm running eZ publish on PostgreSQL 7.2.1 test server here.
> I will upgrade to 7.3 and verify that everything is working
> there as well.

Ok, after the initial Setup, postgres complains 7 times "ERROR: Cannot insert a duplicate key into unique index ezcontentobject_name_pkey"

an during use, a lot of " ERROR: LIMIT #,# syntax not supported.
Use separate LIMIT and OFFSET clauses."
arise.

Jonas Vis

Friday 07 February 2003 8:20:59 am

> At my site, it always crashs and complains about missing
> objects in the admin interface. does anybody have made the
> same experience? or has some pgsql user it fully running?

Think it is the same problem as with 2.2.7 and 2.9.6.
EzPublish uses '' instead of '0' for integers without a value.

Christoph Nelles

Friday 07 February 2003 12:21:47 pm

> Think it is the same problem as with 2.2.7 and 2.9.6.
> EzPublish uses '' instead of '0' for integers without a
> value.

Yeah, you´re right. i´ve checked the postgres log and found a lot of "ERROR: pg_atoi: zero-length string". that would be the error message for this.
but the more obvious error is the use of "LIMIT #,#". Support for this style of the LIMIT clause was dropped in 7.3.x . now you have to use "LIMIT # OFFSET #". The fix for this is easily done (sorry, i am to stupid for using diff :( )
and after the DB setup i get 7 times the error : "ERROR: Cannot insert a duplicate key into unique index ezco
ntentobject_name_pkey"

does anybody know how i can enable logging of wrong queries in postgresql? it worked the last time i needed it (around 7.3.0) but now he logs only the error messages :(

Claus Jensen

Friday 21 March 2003 5:33:05 am

> > At my site, it always crashs and complains about missing
> > objects in the admin interface. does anybody have made
> the
> > same experience? or has some pgsql user it fully
> running?
>
> I'm running eZ publish on PostgreSQL 7.2.1 test server here.
> I will upgrade to 7.3 and verify that everything is working
> there as well.
>
> --bård

Is postgresql known to be working on postgres 7.3.2?

thanks,
claÜs

Claus Jensen

Friday 21 March 2003 5:33:05 am

> > At my site, it always crashs and complains about missing
> > objects in the admin interface. does anybody have made
> the
> > same experience? or has some pgsql user it fully
> running?
>
> I'm running eZ publish on PostgreSQL 7.2.1 test server here.
> I will upgrade to 7.3 and verify that everything is working
> there as well.
>
> --bård

Is postgresql known to be working on postgres 7.3.2?

thanks,
claÜs

Claus Jensen

Friday 21 March 2003 5:33:05 am

> > At my site, it always crashs and complains about missing
> > objects in the admin interface. does anybody have made
> the
> > same experience? or has some pgsql user it fully
> running?
>
> I'm running eZ publish on PostgreSQL 7.2.1 test server here.
> I will upgrade to 7.3 and verify that everything is working
> there as well.
>
> --bård

Is postgresql known to be working on postgres 7.3.2?

thanks,
claÜs

Claus Jensen

Friday 21 March 2003 5:33:05 am

> > At my site, it always crashs and complains about missing
> > objects in the admin interface. does anybody have made
> the
> > same experience? or has some pgsql user it fully
> running?
>
> I'm running eZ publish on PostgreSQL 7.2.1 test server here.
> I will upgrade to 7.3 and verify that everything is working
> there as well.
>
> --bård

Is postgresql known to be working on postgres 7.3.2?

thanks,
claÜs

Claus Jensen

Friday 21 March 2003 5:33:05 am

> > At my site, it always crashs and complains about missing
> > objects in the admin interface. does anybody have made
> the
> > same experience? or has some pgsql user it fully
> running?
>
> I'm running eZ publish on PostgreSQL 7.2.1 test server here.
> I will upgrade to 7.3 and verify that everything is working
> there as well.
>
> --bård

Is postgresql known to be working on postgres 7.3.2?

thanks,
claÜs

Jonas Vis

Friday 21 March 2003 5:49:41 am

> > > At my site, it always crashs and complains about
> missing
> > > objects in the admin interface. does anybody have made
> > the
> > > same experience? or has some pgsql user it fully
> > running?
> >
> > I'm running eZ publish on PostgreSQL 7.2.1 test server
> here.
> > I will upgrade to 7.3 and verify that everything is
> working
> > there as well.
> >
> > --bård
>
> Is postgresql known to be working on postgres 7.3.2?
>
> thanks,
> claÜs

It wont work with pgsql 7.3.x. There are two main problems.
http://developer.ez.no/bug/bugview/1859/

1) "LIMIT #,#" should be "LIMIT # OFFSET #"
2) ez tries to insert/update fields which it dont have values for.

Jonas Vis

Friday 21 March 2003 5:49:41 am

> > > At my site, it always crashs and complains about
> missing
> > > objects in the admin interface. does anybody have made
> > the
> > > same experience? or has some pgsql user it fully
> > running?
> >
> > I'm running eZ publish on PostgreSQL 7.2.1 test server
> here.
> > I will upgrade to 7.3 and verify that everything is
> working
> > there as well.
> >
> > --bård
>
> Is postgresql known to be working on postgres 7.3.2?
>
> thanks,
> claÜs

It wont work with pgsql 7.3.x. There are two main problems.
http://developer.ez.no/bug/bugview/1859/

1) "LIMIT #,#" should be "LIMIT # OFFSET #"
2) ez tries to insert/update fields which it dont have values for.

Jonas Vis

Friday 21 March 2003 5:49:41 am

> > > At my site, it always crashs and complains about
> missing
> > > objects in the admin interface. does anybody have made
> > the
> > > same experience? or has some pgsql user it fully
> > running?
> >
> > I'm running eZ publish on PostgreSQL 7.2.1 test server
> here.
> > I will upgrade to 7.3 and verify that everything is
> working
> > there as well.
> >
> > --bård
>
> Is postgresql known to be working on postgres 7.3.2?
>
> thanks,
> claÜs

It wont work with pgsql 7.3.x. There are two main problems.
http://developer.ez.no/bug/bugview/1859/

1) "LIMIT #,#" should be "LIMIT # OFFSET #"
2) ez tries to insert/update fields which it dont have values for.

Jonas Vis

Friday 21 March 2003 5:49:41 am

> > > At my site, it always crashs and complains about
> missing
> > > objects in the admin interface. does anybody have made
> > the
> > > same experience? or has some pgsql user it fully
> > running?
> >
> > I'm running eZ publish on PostgreSQL 7.2.1 test server
> here.
> > I will upgrade to 7.3 and verify that everything is
> working
> > there as well.
> >
> > --bård
>
> Is postgresql known to be working on postgres 7.3.2?
>
> thanks,
> claÜs

It wont work with pgsql 7.3.x. There are two main problems.
http://developer.ez.no/bug/bugview/1859/

1) "LIMIT #,#" should be "LIMIT # OFFSET #"
2) ez tries to insert/update fields which it dont have values for.

Jonas Vis

Friday 21 March 2003 5:49:41 am

> > > At my site, it always crashs and complains about
> missing
> > > objects in the admin interface. does anybody have made
> > the
> > > same experience? or has some pgsql user it fully
> > running?
> >
> > I'm running eZ publish on PostgreSQL 7.2.1 test server
> here.
> > I will upgrade to 7.3 and verify that everything is
> working
> > there as well.
> >
> > --bård
>
> Is postgresql known to be working on postgres 7.3.2?
>
> thanks,
> claÜs

It wont work with pgsql 7.3.x. There are two main problems.
http://developer.ez.no/bug/bugview/1859/

1) "LIMIT #,#" should be "LIMIT # OFFSET #"
2) ez tries to insert/update fields which it dont have values for.

Christoph Nelles

Friday 21 March 2003 5:59:38 am

> Is postgresql known to be working on postgres 7.3.2?

Yes, PostgreSQL works with postgresql 7.3.2 ;)

Jonas gave you already the right answer. I think, we we´ll have to wait a long time for good PgSQL support.

Has anybody recently checked their Source repository?

Christoph Nelles

Friday 21 March 2003 5:59:38 am

> Is postgresql known to be working on postgres 7.3.2?

Yes, PostgreSQL works with postgresql 7.3.2 ;)

Jonas gave you already the right answer. I think, we we´ll have to wait a long time for good PgSQL support.

Has anybody recently checked their Source repository?

Christoph Nelles

Friday 21 March 2003 5:59:38 am

> Is postgresql known to be working on postgres 7.3.2?

Yes, PostgreSQL works with postgresql 7.3.2 ;)

Jonas gave you already the right answer. I think, we we´ll have to wait a long time for good PgSQL support.

Has anybody recently checked their Source repository?

Christoph Nelles

Friday 21 March 2003 5:59:38 am

> Is postgresql known to be working on postgres 7.3.2?

Yes, PostgreSQL works with postgresql 7.3.2 ;)

Jonas gave you already the right answer. I think, we we´ll have to wait a long time for good PgSQL support.

Has anybody recently checked their Source repository?

Christoph Nelles

Friday 21 March 2003 5:59:38 am

> Is postgresql known to be working on postgres 7.3.2?

Yes, PostgreSQL works with postgresql 7.3.2 ;)

Jonas gave you already the right answer. I think, we we´ll have to wait a long time for good PgSQL support.

Has anybody recently checked their Source repository?

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.