Take a tour of the Busan Cruise Port from our Asia Cruise. Officially the Busan Port International Cruise Terminal (부산연안여객터미널) or Yeongdo-gu Cruise Terminal, this was where we began a beautiful day in the city for us as part of our 14 Day Asia cruise on the Majestic Princess (盛世公主號). The cruise line (in our case Princess cruises) took care of immigration for us, so we pretty much just walked off the ship and through the port terminal building without any delay.
Right outside the Busan cruise terminal building was a trailer setup by a Korean bank where you can exchange money for Korea Won. The exchange rate wasn't great but it was convenient, just expect to wait 10+ minutes with all fellow cruise guests wanting to change money as well.
Princess offered a paid shuttle of $20 per person that would take us to Hotel Foret, which was not an area we were looking to visit. We wanted to visit the famous Jagalchi fish market and Busan Tower, which we did via the easier and cheaper Busan Metro subway system of the city. So we took the FREE shuttle that dropped us off at the Busan Metro Train Station instead (last return train was at 4:20 PM, all aboard time 5:00 PM at the ship). The shuttle took about 15 minutes to reach the station. We then visited the famous Jagalchi fish market via the Busan metro subway- see our video here: https://www.youtube.com/watch?v=AaAMEgZ08ZA
Finally enjoy a beautiful sail away from Busan on our cruise ship at sunset, including going underneath the Busan Harbor Bridge (부산항대교).
This was part of our March 2018 Asia Cruise on the Majestic Princess cruise ship.
A trigger is a named PL/SQL unit that is stored in the database and executed ( fired ) in response to a specified event that occurs in the database.
Overview of Triggers.
A trigger is a named program unit that is stored in the database and fired (executed) in response to a specified event. The specified event is associated with either a table, a view, a schema, or the database, and it is one of the following:
A database manipulation (DML) statement ( DELETE , INSERT , or UPDATE )
A database definition (DDL) statement ( CREATE , ALTER , or DROP )
A database operation ( SERVERERROR , LOGON , LOGOFF , STARTUP , or SHUTDOWN )
The trigger is said to be defined on the table, view, schema, or database.
A DML trigger is fired by a DML statement, a DDL trigger is fired by a DDL statement, a DELETE trigger is fired by a DELETE statement, and so on.
An INSTEAD OF trigger is a DML trigger that is defined on a view (not a table). The database fires the INSTEAD OF trigger instead of executing the triggering DML statement. For more information, see Modifying Complex Views (INSTEAD OF Triggers).
A system trigger is defined on a schema or the database. A trigger defined on a schema fires for each event associated with the owner of the schema (the current user). A trigger defined on a database fires for each event associated with all users.
A simple trigger can fire at exactly one of the following timing points :
Before the triggering statement executes.
After the triggering statement executes.
Before each row that the triggering statement affects.
After each row that the triggering statement affects.
A compound trigger can fire at more than one timing point. Compound triggers make it easier to program an approach where you want the actions you implement for the various timing points to share common data. For more information, see Compound Triggers.