(Migrated) SQL connections and the lack of ms sql server as an engine choice in the gui

Community support
#1

(This message has been automatically imported from the retired mailing list)

Hi, just a quick question

I notice that I can choose oracle, postgre and mysql, but not ms sql
server, as engine in the sql connection gui

Is that by design?

Thanx

-Bad

#2

On 11/11/14 20:24, Baad Sequel wrote:

I notice that I can choose oracle, postgre and mysql, but not ms sql
server, as engine in the sql connection gui

Is that by design?

Hi Baad,

it’s by design in the sense that it has not been designed and
implemented yet :slight_smile:

In other words, it definitely can be added.

Please have a look at this ticket on GitHub which added MySQL:

This means a few lines of code should suffice - would be cool if you
could give it a try?

However, our ensuring that it works with major SQL Server versions, that
all the features work fine, that all tests pass, is a different thing
and I’m afraid it’s too late to do it before 2.0. But for the next
release, sure, why not.

#3

On 11/11/14 20:24, Baad Sequel wrote:

I notice that I can choose oracle, postgre and mysql, but not ms sql
server, as engine in the sql connection gui

Is that by design?

Hi Baad,

it’s by design in the sense that it has not been designed and
implemented yet :slight_smile:

In other words, it definitely can be added.

Please have a look at this ticket on GitHub which added MySQL:

This means a few lines of code should suffice - would be cool if you
could give it a try?

However, our ensuring that it works with major SQL Server versions, that
all the features work fine, that all tests pass, is a different thing
and I’m afraid it’s too late to do it before 2.0. But for the next
release, sure, why not.