Re: Storing hierarchical information?

>If you are using Java, and you can spare an hour to have a look at our
>samples, you might be able to save yourself a lot of brainwork and
>implementation time.

Carl,

Unfortunately, I'm not using Java for this particular application, I'm using PHP. My Java experience is rather limited, but I tend to pick things up pretty quickly, so I don't think this is a major problem. PHP also has an extension which lets you create instances of Java objects as though they were native PHP objects, so I could probably just use that, once I figure out how to get Java working on this box (I'd like it for another, completely unrelated, project anyway).

Since my database access code all in one place and I already use object orientation to an extent, this looks like it would be a perfect fit for what I'm doing and not that hard to implement either. The only thing that concerns me is the phrase "single user, single thread, no transactions" on the Products page. Does this mean that only one process can be accessing the database at any one time?

If concurrent access is possible, I'll give it a whirl and try storing some of the larger documents in there.

Thanks!
-- Dave Kimmel

   criscokid_at_v-wave.com
   ICQ: 5615049 Received on Mon May 07 2001 - 23:37:24 CEST