Version outdated/broken

[tmgast]

Just a heads up, the latest version tag includes old broken connection configuration for postgres, attempts to load queries.postgres but the file is actually queries.postgresql in that version of the codebase.

[Xemptuous]

Thanks for pointing that out. Tbh, I'm not sure why I included release tags when master is what should be used with most nvim plugin managers anyway. I think I was just experimenting with that functionality. Are you opposed to me just removing the releases in general, or do you see any possible problems with that?

[tmgast]

I'm not really sure what the behavior would be if no release versions exist (or versions are removed after already having it installed). Worst case, if it fails after removing them, we could just create a new one and consider adding an action to automate new version tags on merge or something like that.

Noting here incase there are problems, current version is 0.1.1

[MikeLemo1]

Whenn I haven't touched SQLua in over two weeks since last time I managed to get it to work connect to a postgresql db and queriing it from SQLua but now all of a sudden when I try to connect to the database I get:

Error executing Lua callback: .../share/nvim/lazy/lazy.nvim/lua/lazy/core/handler/cmd.lua:48: Vim:Error executing Lua callback: ...ocal/share/nvim/lazy/sqlua.nvim/lua/sqlua/connection.lua:20: attempt to index local 'con' (a nil value)

[MikeLemo1]

Whenn I haven't touched SQLua in over two weeks since last time I managed to get it to work connect to a postgresql db and queriing it from SQLua but now all of a sudden when I try to connect to the database I get:

Error executing Lua callback: .../share/nvim/lazy/lazy.nvim/lua/lazy/core/handler/cmd.lua:48: Vim:Error executing Lua callback: ...ocal/share/nvim/lazy/sqlua.nvim/lua/sqlua/connection.lua:20: attempt to index local 'con' (a nil value)

anyway's fixed this problem by slightly edit the naming of the postgre url interperter so it can use the EXACT url scheme I regularly used so far and is familier with with was the cause of the error but maybe I / my md got confused at some point since the repo hasn't been updated since I last used it.