-
I love using pkgx - great job on the developer experience! One of my projects uses For example, when I write SQL for .load /home/me/.sqlpkg/asg017/ulid/ulid0
select ulid(); Without the extension What are your suggestions about how to proceed with dynamic extensions acquisition, download, and referencing for packages that |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Firstly, super glad you like In answer to your Q. if there's a good PM then generally we would say: package that and use that. However we totally are up for expanding what pkgx can do if required. An example of what we already do is eg with We would go as far as to patch sqlite with new “commands” or whatever sqlite calls them—because we believe packaging should truly be abstracted away because it is tedious—but hopefully we can do something simpler and less intrusive. I think we need some idea of how sqlite extensions work before we can proceed. Probs they are just dynamic libraries right? |
Beta Was this translation helpful? Give feedback.
-
Yes @mxcl you're right -- SQLite loadable extensions are very similar to the
.load /home/me/.sqlpkg/asg017/ulid/ulid0
select ulid(); The job of Does the spec above help? |
Beta Was this translation helpful? Give feedback.
-
well sounds like a standard package then. googling suggests |
Beta Was this translation helpful? Give feedback.
well sounds like a standard package then.
googling suggests
LD_LIBRARY_PATH
is searched by sqlite, if that's true then packaging them and including them in the env will automatically load them without having to specify full paths!