On Sun, Jan 4, 2009 at 12:35 PM, Adam Royle <[email protected]> wrote: > > Todays databases are designed to handle a crapload of queries, so > don't be afraid to take advantage of this. Just make sure you've got > indexes on the right columns and your queries are using those indexes. > You could possible create another table which is optimised to hold any > database changes made along with a timestamp. >
Well I don't think that because databases are getting better then we should stop writing good code because the database can handle the extra load of a bad written application, at least in my case. The log file I'm processing with the cake shell is being written constantly, and the data that I need from the database could be thousands of registers, so doing several queries to the database per second to bring the same thousand of records each time in most cases just to see if there's a new one seems like a bad idea to me. OTOH being able to notify the cake shell when there's new data that it can query or send it the new data is a much better solution, like with a web service, but I don't know if I can use them with a cake shell. Cheers, -- Juan Luis. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
