In MMBase 1.7's new storage system, this will be the default for Postgresql.About the storage && postgresql: Has this been tested?
Yes, we are curerntly running a website on postgresql with 1.7
Is the database structure the same?
All blob fields are removed from postgresql tables, because the data is not stored in the database any more.
Are there the same checks?
What checks?
Is it backwards / forwards compatible?
Forwards compatible? To what? This is the new system.
As to backwards compatible, 1.7 still contains the old support classes, so unless you change your configuration, nothing changes. You needf to turn on the new storage in 1.7
In 1.8, teh old classes will be removed and the new storage system will be default. This emans you ahve one release for switching to the enw storage, either by adapting the database or by creating a new postgresql configuration resource, and igf needed an extension on the storage class.
The reason why i ask this is, since there are some -silly- transactions
/ commit's needed in certain versions, which in other versions lead to
an error(and yes, this is in the situation of byte thingies).
Which is why we don't store blobs in the database any more. However, all commits are done in transactions now, so this might solve the problem. Then again, I am unsure. I personally do not feel much from adding 3+ postgresql classes to storage if you can circumvent all problems by storing blobs on disk.
(and yes, the lookup.xml in the cvs doesnt do the right job. With what in mind was this changed?(we could also say that versions before 7.3-server are supported by the support classes))
I don't have much reason to assume that the postgresql storage implementation does not work on older postgresql version, but I only tested 7.3.
As I said, blobs are not an issue anymore, and the storage does not use weird stuff like triggers. So barring any total hicups in postgresql software, it should work. I woudl welcome people testing it, ofcourse.
As to the storage lookup xml, I noticed postgresql isn't in there. I will add it.
What is the status of the storage? (have there been changes to the api? / is it possible to still make some minor changes?)
Storage is totally overhauled. All code is new, and the API of storage '1.6' and storage '1.7' are totally different.
-- Pierre van Rooden Mediapark, C 107 tel. +31 (0)35 6772815 "Never summon anything bigger than your head."
