Re: metadata confusion for new perl CMS

Just as you were posting I found the SPOPS module. It bears more reading. I'm initially put off by its required modules and complexity, but it might do the trick. I'm also trying to understand the Class::Prototyped module and how it might fit into this... Ahh... so many modules, so little time... But I really am hoping to stay away from DBI.

Comment on Re: metadata confusion for new perl CMS

Replies are listed 'Best First'.
Re: Re: metadata confusion for new perl CMS by perrin (Chancellor) on Jan 10, 2002 at 08:30 UTC
You may be put off by the complexity of SPOPS because you haven't fully understood the complex things you are going to need to do to make your idea work. For example, staying away from DBI might sound good now, but if this thing works you may want to use it for a project with many concurrent users. A database like Postgres will handle the locking and concurrency issues well. If you roll your own with Storable, you will end up needing to do that yourself some day.	[reply]

Replies are listed 'Best First'.

Re: Re: metadata confusion for new perl CMS
by perrin (Chancellor) on Jan 10, 2002 at 08:30 UTC

You may be put off by the complexity of SPOPS because you haven't fully understood the complex things you are going to need to do to make your idea work. For example, staying away from DBI might sound good now, but if this thing works you may want to use it for a project with many concurrent users. A database like Postgres will handle the locking and concurrency issues well. If you roll your own with Storable, you will end up needing to do that yourself some day.

[reply]