Dan McGhan
@dmcghan.bsky.social
Software Development Engineer at Oracle. ❤️ Oracle Application Express (APEX), Oracle Database, CI/CD & JavaScript. Views are my own, not Oracle's.
What if there were people behind you and they sprang out after you heard the count? Would it update you?
No wait, there’s four of them!
No wait, there’s four of them!
September 13, 2025 at 1:56 AM
What if there were people behind you and they sprang out after you heard the count? Would it update you?
No wait, there’s four of them!
No wait, there’s four of them!
Reposted by Dan McGhan
Really like them!
trivadis.github.io/plsql-and-sq...
trivadis.github.io/plsql-and-sq...
PL/SQL & SQL Coding Guidelines
trivadis.github.io
May 16, 2025 at 12:50 PM
Really like them!
trivadis.github.io/plsql-and-sq...
trivadis.github.io/plsql-and-sq...
I remember reporting this bug over a year ago. :) It was patched in 19.23 too.
May 7, 2025 at 2:34 PM
I remember reporting this bug over a year ago. :) It was patched in 19.23 too.
Reposted by Dan McGhan
We got a great overview of the capabilities of the new SQLcl Project feature. No better person to present it than @apexconsulting.nl - one of the first to use it for his CI/CD pipeline in production! In my opinion - the way APEX (and database) versioning and deployment will be done in the future 💡
April 12, 2025 at 9:59 AM
We got a great overview of the capabilities of the new SQLcl Project feature. No better person to present it than @apexconsulting.nl - one of the first to use it for his CI/CD pipeline in production! In my opinion - the way APEX (and database) versioning and deployment will be done in the future 💡
Though, Oracle did finally drop ‘from dual,’ so one never knows...
March 5, 2025 at 6:33 PM
Though, Oracle did finally drop ‘from dual,’ so one never knows...
I agree with your logic, but I think it’s easy to see that some of SQL’s awkwardness is routed in English’s.
Is it worth “fixing”? I don’t know. We need something apolitical to complain about these days. Something that unites us! 😉
Is it worth “fixing”? I don’t know. We need something apolitical to complain about these days. Something that unites us! 😉
March 5, 2025 at 2:37 PM
I agree with your logic, but I think it’s easy to see that some of SQL’s awkwardness is routed in English’s.
Is it worth “fixing”? I don’t know. We need something apolitical to complain about these days. Something that unites us! 😉
Is it worth “fixing”? I don’t know. We need something apolitical to complain about these days. Something that unites us! 😉
“Get the milk and bread from Aldi” vs “From Aldi, get the milk and bread”… 🤪
March 4, 2025 at 9:13 PM
“Get the milk and bread from Aldi” vs “From Aldi, get the milk and bread”… 🤪
Hi Patrizia, firstly, thanks for reporting the issues you found in the SQLcl Forum.
Have you tried running:
project config -list -verbose
Perhaps there'll be an equivalent in the doc some day, but that command is your best bet for now.
Have you tried running:
project config -list -verbose
Perhaps there'll be an equivalent in the doc some day, but that command is your best bet for now.
February 25, 2025 at 6:39 PM
Hi Patrizia, firstly, thanks for reporting the issues you found in the SQLcl Forum.
Have you tried running:
project config -list -verbose
Perhaps there'll be an equivalent in the doc some day, but that command is your best bet for now.
Have you tried running:
project config -list -verbose
Perhaps there'll be an equivalent in the doc some day, but that command is your best bet for now.
In the beginning, SQLcl Projects can feel intimidating. Lot's of commands, processes, etc. But after a few weeks it should start to feel more natural. Once you get to that point, undoing things that commands like stage and release do should be simpler.
February 25, 2025 at 1:40 AM
In the beginning, SQLcl Projects can feel intimidating. Lot's of commands, processes, etc. But after a few weeks it should start to feel more natural. Once you get to that point, undoing things that commands like stage and release do should be simpler.
I'm unaware of any ties in SQLcl Projects to Git tags, so any strange behavior there should be revisited. Please let us know if you have a reproducible test case.
I suspect the true issue was the one you mentioned later, the fact that the main changelog still had points to the deleted release.
I suspect the true issue was the one you mentioned later, the fact that the main changelog still had points to the deleted release.
February 25, 2025 at 1:37 AM
I'm unaware of any ties in SQLcl Projects to Git tags, so any strange behavior there should be revisited. Please let us know if you have a reproducible test case.
I suspect the true issue was the one you mentioned later, the fact that the main changelog still had points to the deleted release.
I suspect the true issue was the one you mentioned later, the fact that the main changelog still had points to the deleted release.
Hi Plamen, did you happen to see this post? danmcghan.hashnode.dev/upgrading-sq...
I recommend refreshing 'src/database'. That would have addressed the issue you ran into with the .pks/.pkb extensions changing to .sql. It would also fix other issues that can happen with updates to SQLcl Projects.
I recommend refreshing 'src/database'. That would have addressed the issue you ran into with the .pks/.pkb extensions changing to .sql. It would also fix other issues that can happen with updates to SQLcl Projects.
Upgrading SQLcl When Using SQLcl Projects
Keeping your development tools up to date is essential for smooth collaboration and to take advantage of the latest features and fixes. When working with SQLcl Projects, upgrading SQLcl requires a str...
danmcghan.hashnode.dev
February 25, 2025 at 1:34 AM
Hi Plamen, did you happen to see this post? danmcghan.hashnode.dev/upgrading-sq...
I recommend refreshing 'src/database'. That would have addressed the issue you ran into with the .pks/.pkb extensions changing to .sql. It would also fix other issues that can happen with updates to SQLcl Projects.
I recommend refreshing 'src/database'. That would have addressed the issue you ran into with the .pks/.pkb extensions changing to .sql. It would also fix other issues that can happen with updates to SQLcl Projects.