Re^2: Threads and MySQL

Thanks guys, I've been looking over what I need the program to do and can't find any reason to continue using threads (I did previously need to share data with the parent and directly between the threads) but with the new version of the program I really don't need any centralized control anymore and the processes can easily share what little data they will be exchanging (only one R/W per hour) via a hash tied to a file (this is even better as it provides a permanent storage of the hash should the system croak for some reason - it'll be able to pick up near where it left off.)

Thanks for the sanity check!

Comment on Re^2: Threads and MySQL

Replies are listed 'Best First'.
Re^3: Threads and MySQL by BrowserUk (Patriarch) on Jan 31, 2005 at 20:01 UTC
If your tasks are using MySQL, why use a shared file (with all the inherent problems of locking etc.) to share data between them? FWIW: The problem with using DBI threads is a design flaw in DBI, not a problem with your code. Examine what is said, not who speaks. Silence betokens consent. Love the truth but pardon error.	[reply]
Re^4: Threads and MySQL by chrispete (Initiate) on Feb 03, 2005 at 21:31 UTC
Two days ago I had a reason to not use the DB for storing that info - now I can't remember what it was, so... ;) Thanks for the help guys, the code is running fine with the fork/exec setup.	[reply]
Re^3: Threads and MySQL by osunderdog (Deacon) on Jan 31, 2005 at 19:57 UTC
Well, KISS is usually the best solution there is! *"Look, Shiny Things!"* is not a better business strategy than compatibility and reuse.	[reply]