Few questions / bugs
First of all, really glad I found Beekeeper studio. Such a breath of fresh air compared to other db managers.
Have a few questions or bugs:
-
The message "see the select box in the bottom left for more query results" is confusing me. Where can I see more results? I don't see any select box?

-
Trying to add a unique constraint to a table, visual bug?
My query:

It seems to work, as I can see it under 'indexes'. But isn't it missing a checkmark under 'unique'?

- Parameters This doesn't seem to work.
When I add $test or :1 to my query, it doesn't prompt me with the parameters. Instead it throws an error:
https://user-images.githubusercontent.com/70519718/171852698-6161587a-c20a-4b76-8304-b99e4b97b393.mp4
Following these instructions https://docs.beekeeperstudio.io/guide/#query-parameters
The owner of this repo doesn't have a whole lot of time so you might be waiting a while for these fixes.
@kars-h Hey! Your first question is referring to this:
If you have multiple queries in the same window and run them all, you will get a little button in the bottom left:

This allows you to go between the different query results:

I hope that helps.
In terms of the query parameters, I typically name the parameters (like :id, or :name) to make my scripts a bit more clear, so I've never really experienced what you're talking about. I do also find it easier to declare the params up at the top:
DECLARE @id uniqueidentifier = :id ;
Maybe try that and see if it works better for you?
Hey! Thanks @theOofDoctor for your response here. @kars-h are any of these still issues? Did you figure out parameters?
I think the parameters parsing is too-strict when using certain dialects. That's an improvement that must be made.
In terms of the unique constraint not showing correctly - what database are you using? (eg MySQL, Postgres)
Thanks for the replies. Sorry I stopped using beekeeper, so I'm not of much use anymore to you.
Re the parameters: I'm reading it back now and realize that I was expecting a pop-up form to input the parameters. Not sure why I expected that, perhaps that is how they do it in DBeaver? So you can consider that a feature request I suppose. But again - I'm not actively using it so no need to do it for me :-)