in reply to An Office In/Out Whiteboard Web Page

Use a database, that's what they're for. It'll hide the locking and concurrency issues for you (most likely :) and you don't have to worry about the details of how your data's stored. If you don't want to go whole hog for something like My or Postgres there's sqlite. You can even use DBD::File to work with your CSV during development and then switch to something else for production (or just go with sqlite to start with and be done with it).

  • Comment on Re: An Office In/Out Whiteboard Web Page

Replies are listed 'Best First'.
Re^2: An Office In/Out Whiteboard Web Page
by OfficeLinebacker (Chaplain) on Jun 15, 2006 at 18:02 UTC
    You're right, why dodge the inevitable? Pretty sure the other whiteboard uses Postgres. I was just too busy or lazy to implement that (I had some experience with XML already).

    For now, I figured out that the hash gets sorted by the length of the key (the new guy has a really short name), so I hacked something to make it work for now.

    Thanks,

    T.

    _________________________________________________________________________________

    I like computer programming because it's like Legos for the mind.

[reply]

In Section Seekers of Perl Wisdom