EBR is also handy for some structural changes, but requires that the application uses editioning views and clean API packages (smart/pink DB).
But usually in reality you will encounter direct table access from applications. ๐
@sartograph.bsky.social
Oracle Database Developer | Patchwork with 5 kids and 5 cats | Likes unicorns, sudokus, bad wordplays & good coffee | prohibited to sing
EBR is also handy for some structural changes, but requires that the application uses editioning views and clean API packages (smart/pink DB).
But usually in reality you will encounter direct table access from applications. ๐
The biggest takeaway imho is to break deployments into small steps (expand/contract), even if they belong to the same feature. This makes it easier to "undo" stuff or even spot the problem.
23.10.2025 08:58 โ ๐ 1 ๐ 0 ๐ฌ 2 ๐ 0Instead of undoing all prior steps, repairing the order, and then doing everything again,
you would just go forward by repairing the order of the remaining steps.
Also, rollback scripts in automated fashion will usually undo every part of the deployment, which might consist of several changes.
A forward fix could focus only on the part which went wrong. Maybe your script just tried to create a FK and the table was not yet existing due to wrong ordering.
So you could just run the failed update script again at a later point as the same version.
Whereas a forward fix is a new deployment (with usual syntax). So you could not run the original patch again and would have to create a new unique changeset to retry the original change.
I think from DB perspective (DDL/data state) the achieved end result of "undoing" is the same.
The difference is the execution with the tools (ie Flyway/Liquibase). Rollback scripts have a special syntax/tags and I think the tools then treat the initial script as "has not been applied".
Warum heiรt es eigentlich alte Blรคtter und nicht Ur-Laub?
19.10.2025 14:40 โ ๐ 2 ๐ 0 ๐ฌ 0 ๐ 0Wieso heiรt eigentlich Schlumpfkacke und nicht Kot d'azur?
21.06.2025 08:32 โ ๐ 3 ๐ 1 ๐ฌ 0 ๐ 0Datagnan and the 3 Musqleteers:
DBAthos, Ratio_to_Reporthos and AWRamis
Code snippet showing Oracle qualified expressions do not work when using subtypes
That is 19c.
Would be so nice if this worked.
Wieso heiรt es eigentlich Samenbombe und nicht Grรผnate?
22.02.2025 14:13 โ ๐ 0 ๐ 0 ๐ฌ 0 ๐ 0Wieso heiรt es eigentlich Farbpalette und nicht Klecksikon?
15.02.2025 11:32 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0Wenn man keine kleinen, klรคffenden Hunde mag... ist man dann intรถlerant?
09.02.2025 11:28 โ ๐ 1 ๐ 0 ๐ฌ 0 ๐ 0Es kรถnnten morgen alle ausreisepflichtigen Menschen ausgewiesen sein und fรผr niemanden hier wรคre auch nur irgendwas besser.
Wohnraum wรคre weiter unbezahlbar, mehr Pflegekrรคfte haben wir davon auch nicht und in der Schule tropft es weiter durch die Decke.
Das ist NICHT unser Hauptproblem.
Wieso heiรt es eigentlich Baum und nicht Zweigstelle?
26.01.2025 15:24 โ ๐ 2 ๐ 2 ๐ฌ 0 ๐ 0After my last blog post, a discussion started about user permissions and CI/CD. So, I wrote a short story about the problem that occurs when using a schema user for application access or in database schema deployments. 
@oracleace.bsky.social 
medium.com/@jasminfluri...
Maybe proxy user would be a good option for the deployment user. Then it doesn't need powerful permissions, we can just grant connect through, maybe even limited to a specific role with only the necessary subset of the schema user permissions.
18.12.2024 19:53 โ ๐ 3 ๐ 0 ๐ฌ 1 ๐ 0I often need to do DML as part of deployments, i.e. data migration, or data "fixes".
I think for audit it is important then that the developers don't have access to the schema users, but only the deployment user, so they can't "go around".
I totally agree with the application user. But could you explain how you would setup the deployment user? Wouldn't it need some CREATE/ALTER/DROP ANY privileges? Then it would be an almighty all-in-one schema-user. How is that better than the schema users directly?
18.12.2024 18:12 โ ๐ 0 ๐ 0 ๐ฌ 1 ๐ 0Schadet nicht, sich das anzuschauen:
www.youtube.com/watch?v=qfYb...
Looking for daily SQL tips, esp when working with Oracle? 
Look no further, just follow
 @sqldaily.bsky.social
Nach einiger Klokrastination heute endlich die verstopfte Toilette unter intensiver Anfeuerung der Frau entstopft.
Sie ist eine wahre Pรถmpelmuse.
Das Erfolgsformat "AskTom" von #Oracle ist nun auf @bsky.app vertreten:
@oracleasktom.bsky.social 
cc/ @chrisrsaxon.bsky.social  @connormcd.bsky.social
A plush oracle database wearing a flat dumbledore hat and a unicorn hand puppet as a beard
Next time I will do that!
For now I came up with... *drumroll*
DBledore!
I even created a fancy dress as suggested by @kibeha.dk 
I made sure to leave a lot of room for improvement.
So I need to find a name for my new partner, too.
Do I go with a modern name like Cloudia or Vectoria?
Or something like Rowland, Bufferdinand, Truncatherine, Schemantha or CurrValery?