This week's book giveaway is in the Kotlin forum.
We're giving away four copies of Kotlin for Android App Development and have Peter Sommerhoff on-line!
See this thread for details.
Win a copy of Kotlin for Android App Development this week in the Kotlin forum!

Mads jacobsen

+ Follow
since Nov 20, 2008
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Mads jacobsen

In the end i solved this using a stored procedure.

Its not really how i wanted to go around it, and from a maintanance point of view its awefull, but given that the structure had a great amount of tables i saw no other choice.
7 years ago
Hi all

i've run into a small problem.

It might be that the solution is obvious, and i just don't see it.

I have a bunch on tables.

I wish to delete a row from the PARENT table, and each corresponding rows from the 3 CHILDX tables.

If the relationship was the other way around, i would just smack a ON DELETE CASCADE constraint on, and live happily ever after.

Does anyone have a suggestion which could point me in the right direction?

I know i essentially have 3 parents and 1 child here, and that the best solution would probably be to inverse the relationship, but this is unfortunatly not an option for me.

btw this is on Oracle Database 11g Enterprise Edition Release if that matters

Thank you in advance for your time.
7 years ago

in particular, my take on it is that the tools and processes should *support* the individuals and their interactions

my point excatly.

But often TDD is described as a methodology itself, ofcourse we can still conclude that if given the chance, individuals and their interactions should be more importent then the process itself.
Thats why i was a bit curious about whether a book on agile testing whould have something discussion about this, as i often see people new to TDD getting caugth up in the process and forgetting about everything else
I guess testing doesn't have to be about that, but i think there is a lot of examples of testing done with many many tools.
And Test Driven Development for instance, have a pre-defined process for your work, and this is considered to be very agile.

but i guess theres a big difference between automated test and non-automated here.
usually automated test will involve a lot of tools and frameworks.
The agile Manifesto clearly states "Individuals and interactions over processes and tools" but usually testing is all about process and tools.
Does Agile Testing discuss this in any way?

Thanks in advance


The main difference between Hibernate and iBatis is that hibernate maps your objects to tables whereas iBatis maps your objects to SQL queries.

You can also consider the fact that even though HQL is great you can do much more with pure SQL, and it might even perform a great deal better with iBatis then Hibernate, as it allows you to take 100% control of the queries executed.
when calling yield(); you allow other threads with higher priority to be executed, if no other threads exsist with higher priority, a thread at random will be picked.
Without knowing what, i suspect that something in your code is causing the executing thread to get a higher priority then the other thread.
try adding a getPriority() call to your code, might be fun to se what the result is