@natalepappalardo it is incomprehensible Sql Server is so neglected.
(not) dogfooding, not much used (because of the obvious issues) - it doesn't help to complain. Let's be constructive with Feedback.
@Karen A But I will say this, if Xojo inc can not provide and maintain reliable database plugins for any specific database that customers can depend on, IMO they would be better off not including it.
In my opinion, it would be in Xojo's best interest to keep it in their portfolio. For many reasons - customers requesting to get it from the same vendor. It's part of what one would expect from such a product. And Natale has given another one:
@natalepappalardo I remind everyone Sql Server is a leading product in the world. also on Linux, now.
So where do we stand? I think Xojo is very much aware that most/all are currently not statisfied with their MSSQLServerPlugin. @Travis H has just fixed one of the reported issues. That shows they are reading along - and working on MSSQL related Cases in Feedback. And one has to assume it's in their interest to provide us with a working "in-house solution" to use MSSQL - otherwise they wouldn't have fixed what has come up so quickly.
But I think it's a fact that fixing this single issue with MSSQLServerPlugin is not enough. It seems there are still some other issues. So please let Xojo know what they are. I've started with what I encountered with this list . I can't test MS-SQL these days - but I would appreciate those reports being looked at again (by Xojo or other developers). Knowing all these issues are solved (or will be, once verified as still-an-issue and fixed) I'd be happy to revisit and use Xojo's Plugin again. Or use it for projects where customers require that.
You might be using MS-SQL in different ways, and encounter other issues. That's why I've asked: Which ones have I missed? Thanks for adding (or submitting) the Feedback Cases.
It's a chance for Xojo to show they want their Plugin to be used. They've just made a start - let's let them know what else we need to be able to use their MSSQLPlugin for our projects and use-cases. Then the chances are good that we see more progress the next days/weeks - and maybe/hopefully have something useful for all parties soon.
Or they may decide it's not in their interest - then I'd tend to agreee with Karen and Bob:
@Bob K I think it would be much better to not include half functioning, buggy, plugins than including them. Why? Because it leaves a (very poor first / negative) experience