Like anonymous PL/SQL blocks, the named blocks will also have the following three parts − Declarative Part It is an optional part.
However, the declarative part for a subprogram does not start with the DECLARE keyword.
Have you ever had one of those moments where you’ve just completed importing 1.7 million user records from flat files into an normalized set of ATG Personalization tables, plus some custom tables, and you only then realize that the passwords from the old system, while in the compatible md5sum format, are all UPPERCASE, while ATG uses all lowercase hashes? I’m happy to override ATG behavior when I should, but this just felt wrong.
I figured the two possible solutions were as follows: The issue with option 1 is that it means overriding the perfectly good out of the box behavior of ATG Profiles for the life of the application due to a set of awkward initial data.
“We are very pleased at the massive adoption of Oracle SQL [email protected]_horse_with_no_name: Oracle does not directly support the JOIN keyword in an UPDATE, but it allows UPDATE involving JOIN operations between table in at least 2 different ways, look at the accepted answer here: stackoverflow.com/questions/2446764/…You could create a trigger on table B that updates table A every time field_2 on table B is updated.The issue with option 2 is that it would take approx 2-3 days.The import process was slow and had to be done in small chunks for reasons I won’t get into now.