Re: Working with tables, best method

<snip>
Then you do the ultimate no-no: you attempt to put some business logic
in your SQL.
</snip>

Huh? I have been putting the business logic in the database for thirty
years. What possible reason would I have for putting the business logic
in the program when it can go into the database and be expressed through
sql?

I have been battling other programmers for that whole time about putting
business logic in programs. (Read a record and then look at some value
and then decide what to do instead of putting a flag or value in the
database, etc).

I want as much of the business logic as possible to be expressed in the
database.