Seth David Schoen asks about procedures, specifically stored procedures. When I was coding in immunohematology, the FDA had to certify our code after it was compiled and before it could be deployed. Thus, we took extra pains to see that ANYTHING that would otherwise be in code wasn't. None of our sql statements were (they were stored in text files or stored procedures). Stored procedures were relatively easy to change, but difficult to maintain across databases.

While I've been a DBA, I didn't use them overmuch. I think the reasons DBAs like them is that they spend a lot of their time in sqlplus (or the non-Oracle equivalent thereof) and therefore aren't accessing a database through code 99% of the time. Thus, stored procedures are a convenient means of access for them.

I didn't do much coding over the weekend, giving my eyes a rest. Rick and I went to see Terry Pratchett. While we planned to go on Saturday to Future Fantasy, we found we had more access at Kepler's. We listened to him prattle off for a while then went to the cafe.

I read the first two Honor Harrington books, which I enjoyed a lot.

I worked a bit on CottonBale, which I should have done in a few days.