-
Notifications
You must be signed in to change notification settings - Fork 862
MS SQL Connector #1642
Comments
When you can expect a working connector to Ms SQL ?? |
I need this too |
Hey @SebaBoler and @iamgmd, thanks a lot for your interest in the MS SQL connector 🙂 You can read more contributing to a DB connector here. |
Super excited about this, though I will probably fall back on the hosted platform as I'm getting tired of managing everything - the NET community is ~desperate for a GraphQL API interface to SQL Server. |
I noticed MS SQL was missing on the main README: https://github.com/graphcool/prisma. |
This comment has been minimized.
This comment has been minimized.
1 similar comment
This comment has been minimized.
This comment has been minimized.
I waiting for this |
I need this badly |
Thanks a lot for your feedback everyone 🙂 If you have any thoughts in the spirit of what I mentioned above, I'd be happy to hear it! |
I really need this! Please make this happen! |
This comment has been minimized.
This comment has been minimized.
2 similar comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
There is a huge .NET community - by supporting MSSQL and writing some how-to's on deploying onto Azure I think you will capture some massive traction in the enterprise space - especially financial services. |
Big +1 on this. Regarding features even just reproducing the pgsql functionality would solve 90% of users needs. |
This is important because there are lots of enterprise organizations as @develomark mentioned, which use MS SQL and they will be able to start using Prisma (I'll be one who will suggest them to try), hope it will happen soon :) Also I'll take a look current connectors and I'll try to share something valuable about that. One note here, if you will support azure sql, ms sql will be supported also, because azure sql is limited version of ms sql, but those limits will not have any effects for Prisma. |
I also would like to take a vote for a MSSQL connector to
Since I have become a user of MSSQL I must say it's a great DBMS and I would like to start a GraphQL project with some of our customers. Therefore I would like to have a solid development library that fits with SQL Server and is capable of using some more of the TSQL features and is not limited to a a really small subset of the SQL standard. One could say to go with .NET/.NET Core but making Prisma available as a JavaScript solution to the market would propably also accell the need and use of full stack JS developers that could create products for big enterprise customers. |
hope this . |
This comment has been minimized.
This comment has been minimized.
@Gary-Shurgin Not sure if your post is relevant in this thread as this one is related to wanting MS SQL in Prisma, nothing to do with MySQL. |
This connector should be shipped by default as soon as possible.
|
I think you can add support to this through the Microsoft SQLServer JDBC library ? Code should be similar to what you have done with MySQL and PostgreSQL. You might also need to consider supporting different versions : Microsoft team has also been open-sourcing lot of stuff related to SQL Server lately, may be we can ask their help. Check out the Linux tools they have released: I am using these tool at work in a Linux / Scala environment with connection to Windows / SQL Server backends. But not using GraphQL for the moment. |
Would like to know whether the work on this has started or not? Dont see a branch for it either. |
I need this so badly, at this moment I use TypeORM because of this, if we have MS SQL Server Connector, for sure I change for Prisma. |
Do we have any timelines for this? Keen to see or contribute to this as it will greatly help when building for enterprises that work only with MS SQL due to legacy implementations. |
I need it badly too. any update yet? |
I don't understand why no one reply. I understand that actually there aren't any intention of doing some efforts; but I don't understand why no one is explicitly saying this. |
Typeorm or sequenlize could be alternatives solution. But they are not designed for gql specifically. |
This is annoying. MS Sql is still in the top 3 most used DBs world wide, double more used than Postgres that already has the connector. Also if it not deserves a connector yet, I think may deserves a reply at least |
Is this due to the different type of connection. I see on W3 that you simply import mysql and connect, where as a msSql database needs an odbc connection. It would make sense then that a connection like this might take longer and work differently with the infrustructure. It would be a cool feature to have. Is there a way to use a node server as a middleware for this. Could we use a node server connecting through odbc then pass that to prisma directly from the query response? https://www.tutorialsteacher.com/nodejs/access-sql-server-in-nodejs |
@JesseHenson The silence NO. |
if you really need sth for mssql database connector badly. There is another open source library called sql datasource, it’s been recommended by Apollo offical document(you should be able to find it y reading doc of Apollo-datasource-rest)You can find it from Github(https://github.com/cvburgess/SQLDataSource/blob/master/README.md#sqldatasource). It’s based on knex and Apollo-datasource. It provides huge flexibility to build a ms sql server based datasource connector at gql server, it has some good features such as batching, transactions and simple syntax. Try it with dataloader would be a way to go if you can’t wait prisma’s new release. Hope it helps. |
I have done this and it is not that difficult If anyone wants to see a SOLID implementation check out the "The road to graphql" by Robin Wieruch Full walk though |
Prisma 2 is currently being rewritten using Rust instead of Scala. Are any more DB connectors being written for Prisma 1? Or is the plan to wait until Prisma 2 is out before any more are written? And at that point we may expect to have a SQL Server DB connector? |
Is it a good day to ask about ETA? Or even to ask about EST? But... it's a shame that most of the people are cut off because of the lack of connectors |
Hey, for anyone trying to help out here, but hitting that 404: It's not too bad to correct the link. Just change 'graphcool' to 'prisma' and the link will work. That will help, because the next link is full of links that 404 too 😆 |
What problem are you trying to solve? Is it that you want to do GraphQL with SQL Server or is it that you want to specifically use Prisma with SQL Server? |
The final target
The final target is obtaining a GraphQL with SQL Server, with subscriptions, schema migrations and all the good stuff of PRISMA. So, probably... The final target is obtaining PRISMA for SQL Server? I've seen another great tool, also that only for Postgres Hasura |
Sorry, but everything is a mess... Do we need to wait here the connector even for Prisma 2, Prisma Framework or Photon.js ecc...? |
This will be a game changer and I for one would be more than glad to encourage my team to adopting this. Any ETA would be highly appreciated. |
Any insights into where this might fit on the roadmap? |
After 2+ years would be gold :) |
Is there any way to post a bounty towards this feature? |
Bounty or somehow Microsoft buys prisma 😂 |
For prisma 1, I do not think this will happen. For prisma 2, it will probably happen sometime after it is stable, or somebody starts to write this connector. I am told it is a lot easier than for prisma 1. |
Starting a new project and used |
Good luck :) |
Prisma is working on this it seems. They've done a lot work patching this driver: https://github.com/prisma/tiberius If anyone knows Rust and wants to contribute their expertise on this then check out this repo. |
Eagerly waiting on this. Because I need a sql database for my project, I'm currently using MySql and it sucks... |
This feature requests serves as a central place to discuss development and progress for the MS SQL connector.
The text was updated successfully, but these errors were encountered: