Whopsie, forgot a big todo. Give me a moment.

Thank you for the PR. I'll check and test it a bit a come back with suggestion/merging.

I don't know much about mssql, but i created a docker instance, created a table named "test", i am able to connect to it and list all the "instances" and "tables", but when i select a table it shows the following error:

Any idea of why is this happening?

I will check on this as soon as I have time.
I only have an already working remote database and since I am on M1 I cannot really have an local instance.
As I said I will look into this. I am also preparing a PR with some more driver tests if you are interested.

Oh and I did not mention this yet: it's a great project you created here. Props for that. :)

I will check on this as soon as I have time. I only have an already working remote database and since I am on M1 I cannot really have an local instance. As I said I will look into this. I am also preparing a PR with some more driver tests if you are interested.

I'm on M1 also, i just created a docker instance.

Oh and I did not mention this yet: it's a great project you created here. Props for that. :)

Thank you very much, i love this project, i use it daily. I know it is not the best code (first go project), and it have bugs, but with the help of the community we can make this awesome.

Thanks for your time making this PR.

Okay I found the issue. I specified the database directly in my connection string, therefore the DB-Server knew where to run my queries.
I changed it to explictly use the specified DB.
I also added a logger.

I added some todos, since I did not want to refactor a lot of your code without a review first. And it has nothing to do with the matter of this PR.
My suggestion: All methods of the driver interface should be passed the database. You often hide it in the table with a database.tablename notation.
Further I think all driver methods should accept a context.Context as first argument, as it allows easy control on timeout, or application exit or other things. (https://pkg.go.dev/context)

Check it out, and please give me again feedback. I want to see this project moving forward, so I also can integrated in my day-to-day tools set.

Hi,

above problem is indeed solved, but there's still something i noticed today. When you press "2" inside the table view to see the "Columns", it is empty.

Maybe there's a problem in the GetTableColumns function in the driver file.

So the problem is, that even though the drivers interface specifies the GetTableColumns with the parameters database and table, the database is empty, whereas the table is of format database.table.
Apparently I misunderstood the interface, but I think it should be refactored. There should always be a database and a table attribute. The table attribute should never have the database encoded into it. Also I suggest a context.Context is passed, as described in https://pkg.go.dev/context.

I would love to make this a separate PR. For now I will always check if the table param contains a database and if so overwrite database param, I guess.
Change is comming up.

If you have a way for private communication let me know. I would love to here what you say on the interface change. I am sure there is a reason that the database is encoded in the table param, that I just dont know about.

When i try to filter a table, the following error happens:

Apparently I misunderstood the interface, but I think it should be refactored. There should always be a database and a table attribute. The table attribute should never have the database encoded into it. Also I suggest a context.Context is passed, as described in https://pkg.go.dev/context.

I agree that should be refactored