Stew Ashton
@stewashton.bsky.social
Retired IT architect, Oracle developer. If you follow me and we don't seem to have any common interests, I may block you. Sorry, old Twitter reflex...
stewashton.wordpress.com
stewashton.wordpress.com
Come on, that's *one-third off* ! (on the 9s 🫠 )
November 18, 2025 at 11:39 AM
Come on, that's *one-third off* ! (on the 9s 🫠 )
Yes! The 10x net positive is immediately obvious, sorry if I gave another impression.
November 8, 2025 at 5:24 PM
Yes! The 10x net positive is immediately obvious, sorry if I gave another impression.
People who know me better would not even let me *pretend* to be a dba 😱
Both things I mentioned are allowed in LiveSQL, so I assumed growing pains, not a conscious decision. I'll save this kind of thing for the forums henceforth.
Both things I mentioned are allowed in LiveSQL, so I assumed growing pains, not a conscious decision. I'll save this kind of thing for the forums henceforth.
November 8, 2025 at 8:47 AM
People who know me better would not even let me *pretend* to be a dba 😱
Both things I mentioned are allowed in LiveSQL, so I assumed growing pains, not a conscious decision. I'll save this kind of thing for the forums henceforth.
Both things I mentioned are allowed in LiveSQL, so I assumed growing pains, not a conscious decision. I'll save this kind of thing for the forums henceforth.
Yet more remarkable work from you and your teammates! It would be nice, though, to have info on limitations (even if temporary). For example, is it just me or is there no way to see parameters other than NLS? And of course no access to V$SESSION so no execution plans 🤷♂️
Still great work though 👏
Still great work though 👏
November 7, 2025 at 6:56 PM
Yet more remarkable work from you and your teammates! It would be nice, though, to have info on limitations (even if temporary). For example, is it just me or is there no way to see parameters other than NLS? And of course no access to V$SESSION so no execution plans 🤷♂️
Still great work though 👏
Still great work though 👏
I’m waiting a bit longer to get more protection later on for the flu. As for Covid, it’s too close to my last jab right now. No SpongeBob for me 😢
October 14, 2025 at 1:52 PM
I’m waiting a bit longer to get more protection later on for the flu. As for Covid, it’s too close to my last jab right now. No SpongeBob for me 😢
From experience, this is a time of intense activity, fatigue and disorganised reflexion. May your parent rest in peace and may you benefit from all possible support and internal strength 🙏🏻
October 11, 2025 at 8:18 AM
From experience, this is a time of intense activity, fatigue and disorganised reflexion. May your parent rest in peace and may you benefit from all possible support and internal strength 🙏🏻
Where I buy my wine, every bottle of beaujolais is "neuve". If you are buying used beaujolais that's your choice, but it's an unusual one...
October 4, 2025 at 8:46 PM
Where I buy my wine, every bottle of beaujolais is "neuve". If you are buying used beaujolais that's your choice, but it's an unusual one...
Nouveau means just created or a new replacement. Neuf means unused or at least “like new”.
October 3, 2025 at 9:37 PM
Nouveau means just created or a new replacement. Neuf means unused or at least “like new”.
See the banner of my blog : stewashton.wordpress.com
On the way back to Sorento from Capri in January. Also living in France but not where you are 🤷♂️
On the way back to Sorento from Capri in January. Also living in France but not where you are 🤷♂️
wirdpress.com
stewashton.wirdpress.com
September 8, 2025 at 6:26 PM
See the banner of my blog : stewashton.wordpress.com
On the way back to Sorento from Capri in January. Also living in France but not where you are 🤷♂️
On the way back to Sorento from Capri in January. Also living in France but not where you are 🤷♂️
YES to sentences 1 and 3. APEX apps can be "low code", I too did some COVID apps quickly in 2021. Still, many APEX apps are "low code" on the front end but less so on the back end.
What's sad is that so many developers want the opposite: "low code" to the DB and code the heck out of everything else.
What's sad is that so many developers want the opposite: "low code" to the DB and code the heck out of everything else.
September 1, 2025 at 3:29 PM
YES to sentences 1 and 3. APEX apps can be "low code", I too did some COVID apps quickly in 2021. Still, many APEX apps are "low code" on the front end but less so on the back end.
What's sad is that so many developers want the opposite: "low code" to the DB and code the heck out of everything else.
What's sad is that so many developers want the opposite: "low code" to the DB and code the heck out of everything else.
APEX may be "low code" for some, but I see it more as a window to the world for database developers and DBAs. Not really the same thing, in fact one might say "low code" denigrates database development. 2/x
September 1, 2025 at 8:17 AM
APEX may be "low code" for some, but I see it more as a window to the world for database developers and DBAs. Not really the same thing, in fact one might say "low code" denigrates database development. 2/x
I wrote APEX applications for the Paris medical school. Adding DDL, backend code and PL/SQL or SQL embedded in the apps, I am up to almost 8000 lines of code. When we say "low code" it really means "little or no javascript". My son runs a Web dev company and they won't touch my stuff for money. 1/
September 1, 2025 at 8:12 AM
I wrote APEX applications for the Paris medical school. Adding DDL, backend code and PL/SQL or SQL embedded in the apps, I am up to almost 8000 lines of code. When we say "low code" it really means "little or no javascript". My son runs a Web dev company and they won't touch my stuff for money. 1/
If only bikes were equal users and not privileged users! After 37 years in Paris, the only accident in my family was last year when my daughter had her arm broken by a bike collision. No way to hold the cyclist responsible because rules of the road are not precise.
August 31, 2025 at 1:55 PM
If only bikes were equal users and not privileged users! After 37 years in Paris, the only accident in my family was last year when my daughter had her arm broken by a bike collision. No way to hold the cyclist responsible because rules of the road are not precise.
I'm not sure how "obvious" it is. Aside from all the physical, logical, legal and contractual separations, the customer can manage the encryption keys so even if the data was surrendered the feds would have to break the encryption.
As the article states, EU-based tech may have issues too.
As the article states, EU-based tech may have issues too.
July 29, 2025 at 8:44 AM
I'm not sure how "obvious" it is. Aside from all the physical, logical, legal and contractual separations, the customer can manage the encryption keys so even if the data was surrendered the feds would have to break the encryption.
As the article states, EU-based tech may have issues too.
As the article states, EU-based tech may have issues too.
Some software does work like that; it’s just that everybody badmouths it. Think mainframes or SQL.
July 27, 2025 at 10:26 AM
Some software does work like that; it’s just that everybody badmouths it. Think mainframes or SQL.
If your without_merge procedure did the UPDATE first, wouldn't it behave like MERGE?
July 12, 2025 at 4:28 PM
If your without_merge procedure did the UPDATE first, wouldn't it behave like MERGE?
In the MERGE statement, you want a "restart" when the insert fails? The whole statement would have to be rolled back and retried. With UPDATE restart, rows are selected and locked so the restart will always succeed. In a MERGE restart, success would not be guaranteed; how many restarts do you want?
July 12, 2025 at 4:19 PM
In the MERGE statement, you want a "restart" when the insert fails? The whole statement would have to be rolled back and retried. With UPDATE restart, rows are selected and locked so the restart will always succeed. In a MERGE restart, success would not be guaranteed; how many restarts do you want?
Wasn't it a COVID app?
July 3, 2025 at 3:32 PM
Wasn't it a COVID app?
Real speed comes from lower latency, not throughput.
- Instead of waiting for the printed output to come up from the computer room, thus testing twice a day, I now test continuously as I develop.
- With APEX, some design changes can be made *during* customer review meetings, saving weeks.
- Instead of waiting for the printed output to come up from the computer room, thus testing twice a day, I now test continuously as I develop.
- With APEX, some design changes can be made *during* customer review meetings, saving weeks.
July 3, 2025 at 1:21 PM
Real speed comes from lower latency, not throughput.
- Instead of waiting for the printed output to come up from the computer room, thus testing twice a day, I now test continuously as I develop.
- With APEX, some design changes can be made *during* customer review meetings, saving weeks.
- Instead of waiting for the printed output to come up from the computer room, thus testing twice a day, I now test continuously as I develop.
- With APEX, some design changes can be made *during* customer review meetings, saving weeks.
In the '80s as a COBOL developer, I once tracked how my time was spent: writing code was 15% ! When management learned that a new code generation tool, which promised to make me 3 times faster, would at best make me 10% faster, they decided not to buy it 🤷♂️ 1/
July 3, 2025 at 1:12 PM
In the '80s as a COBOL developer, I once tracked how my time was spent: writing code was 15% ! When management learned that a new code generation tool, which promised to make me 3 times faster, would at best make me 10% faster, they decided not to buy it 🤷♂️ 1/
Kunsthistorisches Museum
June 22, 2025 at 7:37 PM
Kunsthistorisches Museum
Sorry, I meant they will go the way of the MODEL clause IF there is no further investment. I fervently wish for further investment in bug fixes, enhancements and documentation that really explains what macros do *and don't do*
June 11, 2025 at 1:38 PM
Sorry, I meant they will go the way of the MODEL clause IF there is no further investment. I fervently wish for further investment in bug fixes, enhancements and documentation that really explains what macros do *and don't do*