2010/4/23 Merlin Moncure <mmoncure@gmail.com>:
>
> There's way too much logic going on there for me to test all the
> different cases.
>
> I suspect this is your problem: you triggered a case somehow which is
> not handled properly via your labyrinth of switches and loops. I
> highly doubt this is a case of database corruption. My advice here
> would be to not rely on procedural code to guard against something
> which can and should be enforced by a constraint. If something is
> wrong (source_id being null), declare it to be wrong -- that way the
> next time this happens the constraint will bounce the transaction and
> you can catch the problem when it happens as opposed to reverse
> engineering it.
>
Thanks for the suggestion and help. Will work on changing the function
and constraints for enforcing data accuracy.
Thanks and regards,
Ma Sivakumar
மா சிவகுமார்
எல்லோரும் எல்லாமும் பெற வேண்டும்
http://masivakumar.blogspot.com