14h
answered Are individual queries faster than joins?
1d
awarded Nice Question
2d
answered Tablespace on ephemeral storage
2d
answered Separate table by often changed / not often changed data?
May
21
answered How do I execute an Oracle SQL script without sqlplus hanging on me?
May
21
comment How do I execute an Oracle SQL script without sqlplus hanging on me?
Why do you want the script to run without user interaction? Is it so that another script after it will also run or so an OS process will run when the script completes? Knowing your goal will help devise the best plan.
May
14
awarded Caucus
May
12
awarded Popular Question
May
9
reviewed No Action Needed Twice job results in sql server, last one is left in progress
May
9
reviewed No Action Needed How can I reliably track stored procedure ( and functions ) use over time?
May
9
reviewed Close How can I reliably track stored procedure ( and functions ) use over time?
May
9
reviewed Approve suggested edit on How can I reliably track stored procedure ( and functions ) use over time?
May
8
comment Oracle 10XE: Stop schemas seeing the all_users table?
@Colin'tHart Indeed, thanks for adding that bit.
May
8
awarded Popular Question
May
7
answered Oracle 10XE: Stop schemas seeing the all_users table?
May
7
comment How do you version your Oracle database changes?
Thanks for posting this.
May
7
awarded Self-Learner
May
6
comment How to design this database to avoid cyclic dependency?
@ypercube Indeed it does; not sure how I got that wire crossed. To be clear you probably shouldn't create an Events table even though it does remove the cyclic dependency.
May
6
comment How to design this database to avoid cyclic dependency?
Removing the constraints removes the cyclic dependency from the definition, but not the design. You could add an Events table to record the UserID and AddressID that last created or modified the address, but that just moves the dependency one step further away. Going the other way, if the User table had CreatedBy and ModifiedBy columns, the cyclic dependency would exist in one table. This is similar to an employee table with a supervisor column where the supervisor is also an employee. As Phil indicated - Not a problem.
May
6
comment Testing AFTER INSERT Trigger
Phil is correct. In addition, you should almost always prefer constraints to triggers. You should also consider having triggers call packages to do the bulk of the functionality. Unlike triggers, packages can be compiled natively and are significantly easier to unit test. You would still need to test the trigger, but the tests would be better focused.
1 2 3 4 5