- 85 entries Alagad
- 12 entries Ant
- 167 entries ColdFusion
- 11 entries ColdSpring
- 20 entries Conferences and Events
- 1 entries Development Tools
- 5 entries Dynamic Programming
- 1 entries Flexmaniacs
- 52 entries General
- 4 entries Groovy
- 5 entries JRun
- 17 entries Jobs
- 17 entries Model-Glue
- 27 entries OO Development
- 53 entries Programming
- 31 entries Reactor For ColdFusion
- 13 entries SQL
- 14 entries The Server Side
- 7 entries Validat
- 8 entries Farcry CMS
- 32 entries Flex
- 10 entries Flex
- 3 entries Hibernate
- 3 entries jQuery
- 1 entries Presentations
- 1 entries Press
Subscribe to our The Alagad Technical Team Blog
Entries Tagged as 'SQL'
Oracle Thin Client and 'ROWID' Wierdness
Be careful when using the Oracle Thin Client JDBC drivers - they behave a little differently than the Oracle JDBC drivers that are shipped with ColdFusion Enterprise and Developer Editions.
Sproc to Cascade Deletes In SQL Server
As a developer, from time to time you need to delete an record out of a database. And, if that record has a number of tables that refer to it by foreign key (and heaven forbid those tables are themselves referenced), deleting a single row can be quite a headache. This wouldn't be so bad if your foreign keys were set to cascade deletes, but they rarely are. In these cases you're pretty much stuck writing a lot of SQL to delete one single record.
For situations like this I've created a stored procedure which will automatically cascade delete records for you. Here's the complete sproc:
Delete Almost Everything From Your MSSQL Database
Ok, this script is dangerous. Use it only when you intend to. If you delete stuff you don't want to, it's your problem!
Anyhow, now that we're past the disclaimer, I'm posting this blog entry as a follow up to one Layne Vincent posted earlier this week on how to truncate most of your tables. As it were, we are currently working on a project where pretty much everything related to the database is scripted. We have a script we generate that will completely rebuild our database including all of it's tables, stored procedures, functions, basic lookup data etc. The problem is, although the script has a chunk of code at the beginning to drop tables, the script takes no account of foreign key constraints and these drops simply don't work. Besides, we also have a lot more than just tables we may want to drop.
