Dearest Monks,
I'm seeking validation and the experiences of others.
I'm creating a content management system and having difficulty with SQL stuff, mainly I have so many properties that I have to take into account that the SQL statements are wicked complicated, and I've spent the last couple of days working on them to no avail. I was trying to do everything with 1 statement, and it just wasn't happening.
I'm creating a complicated reference based data structure, to be passed to a recursive HTML::Template loop. I then got to thinking that I'm going about it the wrong way. Incurring a DBI hit, or multiple DBI hits, would top out my script in terms of performance no matter what.
My thoughts are to create my data structures every five minutes or so with a cron-tabbed script, storing them with Storable, and then opening them in my display module, saving on the DBI overhead.
I'm expecting a bunch of concurrent connections. Assuming I use file locking properly, will this be OK? The Cookbook has a great description of how to get this to work, and I'll probably generalize it into a subroutine.
My questions:
-Any sufficiently advanced technology is
indistinguishable from doubletalk.
In reply to mySQL hits or Storable retrieves? by Hero Zzyzzx
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |