By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,178 Members | 987 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,178 IT Pros & Developers. It's quick & easy.

ORM, XPath, and pgxml_dom segfaulting

P: n/a
Hi,

I'm currently running 7.3.4 on Debian/testing, I've been trying to get
pgxml_dom working but after doing some normal tests I find that it
segfaults the postmaster whenever it hits an error, is this because
the contrib module isn't maintained beyond alpha stage or doesn't it
simply handle anything but completely well-formed documents without
entities etc? Are there any alternatives to this module?

I was thinking of using this for my CMS project, based on storing
class instances in the database, the first version simply serialized
the objects to strings and stuck them in the database but this turned
out to be extremely slow and searching the contents of the documents
was impossible so I'm trying to find other ORM solutions. I seem to
always stop dead when trying to figure out how to do arbitrary joins
on a single table (say a document with attachments, images and a
series of revisions). I've tried doing it via a separate relations
table but that adds a layer of complexity that I would like to avoid.
Any suggestions on where to start on this?
Nov 22 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Tue, 20 Jan 2004 01:07:00 +0000, Simen Brekken wrote:
Hi,

I'm currently running 7.3.4 on Debian/testing, I've been trying to get
pgxml_dom working but after doing some normal tests I find that it
segfaults the postmaster whenever it hits an error, is this because
the contrib module isn't maintained beyond alpha stage or doesn't it
simply handle anything but completely well-formed documents without
entities etc? Are there any alternatives to this module?


There is a new version - which I hope to release within a few weeks.
In answer to your questions - one of the bugs with the old version
related to a memory leak when entities appeared. Also, although it
shouldn't segfault, all the XPath support assumes that your documents
are well-formed, so you'll just get NULL returned in many cases if the
documents aren't well-formed.

Regards

John
--
Nov 22 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.