John and I were supposed to be meeting on a different project, but when we joined the meeting, Eric and Wayne were having a great discussion on scheduling and stored procedures. They were talking about options inside of Adobe ColdFusion (server-side scripting) as well as options inside of MySQL (database stuff). Here are some of my other notes, while Steve, John, and I were listening to their conversation. Good stuff:

- Web stuff, client-side stuff, and server-side stuff. We have to mix and blend all of these technologies. Each one does specific things and shines in certain areas and aspects.

- Lots of great back and forth between both Wayne and Eric - they were talking about phases, threads, business flow, standards, etc. How to process big amounts of data in the most efficient ways.

- Pros and cons about database triggers - one of the best ways to use a trigger is to set a flag in a different table that business logic could then use.

- Along with triggers, they were talking about rolling back and using simple last date modified flags and last modified dates. Then you only have to go back and clean-up or alter what has changed. Lots of good discussions here. Eric had some good insight in this area.

- Most database tables (where needed), should have who created it (an id number), what date was it created, who modified it (if anyone), and what date was it last modified on? - This is not a comprehensive history, but it helps to keep track of general flow processes. The other advantage is that you should be able to tell a rough history (the basics) just by looking at one table. We could then build business logic based on those fields and values.

- Base some of the new logic off of the last modified dates and then prompt for action accordingly.

- Cost is speed

- Changing water into ice analogy - Think of water (liquid or new values) changing into ice (solid data and solid numbers) - water, snow, ice - it, things, become more firm and solid as they move along the process.