This has been the only incompatibility I encountered so far. I am using MMBase 1.6.3
and the JDBC driver 7.3.3.
> -----Oorspronkelijk bericht-----
> Van: Eduard Witteveen [mailto:[EMAIL PROTECTED]
> Verzonden: vrijdag 20 juni 2003 9:28
> Aan: [EMAIL PROTECTED]
> Onderwerp: Re: MMBase vs. Postgresql 7.3
>
>
> Kees Jongenburger wrote:
> >>>If MMBase is supposed to work fine on 7.3.2. than this
> might be a bug
> >>>that should be solved by someone in
> >>>org.mmbase.module.database.support.PostgreSQL72
> > postgress masters backward incompatibility very well and
> with the added value
> > of the jdbc driver that handles blobs in different way's
> for every version it
> > very hard to support the database. This is not a suprise to me. the
> > "function/stored procedure" here was created because with
> postgress we use
> > table inheritance but postgress does't handle
> > foreign-keys wel nor do the constraints on inherited tables
> very well
> > (if in mmbase_object we define number to be unique that
> does not prevent us
> > from creating other entries with the same number)
> >
> > We need to find a good maintainer for the postgres storage
> layer and for now
> > it looks like every postgress version will need it's own
> storage layer.
> Well, if this is the only point on were it misbehaviours, im
> prepared to
> create an Postgres73.java.
> -but- then the lookup.xml should point to the proper classes, and not
> the storage classes (all lookup_postgresql.xml info points to
> postgresql.xml --> org.mmbase.storage.database.PostgreSqlStorage
> Why has this been changed and by whom? (also:
> lookup_postgresql.xml is
> not an valid xml!)
>
>
>
