I've just found SQL Notebooks and am happily integrating them into my workflow. I'm guessing this is an odd use case, but it's one I was testing and the results were “odd” so I figured I'd report them and see what comes of it…
I ran project init -n my-project -s my_schema from a code cell and it appears to have worked fine.
Next I ran a project export -o my_object command in another cell and got a message about not having the connection configured for the project. It appears to have run with the active connection for the notebook, so no worries. I decided to take the suggested course of action and update the config…
I chose to use the project config set command, but as I didn't know what the options and syntax were I had to do a little searching and consult the help project command.
Long story short I ended up running the config statement from a sqlcl terminal, not from another code cell. The result was a SQLcl version conflict error. SQLcl Version Mismatch expected 4.1.0 found 25.4.1.0. Looking in my project.config.json file reveals it does indeed show the version as 4.1.0. I added the 25 prefix and reran the command at the command line successfully. However, running another project command back in a code cell resulted in an error with the versions reversed from above.
Is Notebook reporting its SQLcl version as 4.1.0? and is this intentional?
Thanks