We have just upgraded our database from SQL Server Express to SQL Server 2014 Web Edition.
We are also, and don't ask me why, using Subsonic as our database provider.
As soon as we pointed our code to the new SQL 2014 edition we got errors.
It seems that Subsonic has decided, on some queries that involve paging, to drop Where clauses so that the following And clause causes an error.
Has anyone else experienced any issues with Subsonic and SQL Server 2014 Web Edition.
We are using Subsonic 2.2 and are hesitant to upgrade to 3 unless we know it'll work as this is a major piece of work.
Note
The code works fine with SQL Server 2012 Business edition.
As noted in the comments you need to update the source code for Subsonic.
This is within ..\SubSonic-2.0-master\SubSonic\DataProviders\DataService.cs when you get the code from GitHub.
The area to update is below. Depending how you want to update it but for me using SQL Server 2012 I have just defaulted to Sql2008Generator :-
case DataProviderTypeName.SQL_SERVER:
if(Utility.IsSql2005(provider))
generator = new Sql2005Generator(sqlQuery);
else if(Utility.IsSql2008(provider))
generator = new Sql2008Generator(sqlQuery);
else
generator = new Sql2000Generator(sqlQuery);
break;
Related
Recently I have upgraded my project to Java 11 and postgres to version 12 (flexi server). I have also updated JOOQ to 3.16.2 from 3.12. Since these upgrade code generation is not happening for the new tables created in postgres.
e.g. before the above upgradation for a particular schema let’s say there were 10 tables. And after upgradation I have added 2 new tables. Now code generation is not happening for the 2 newly created tables. For old tables code generation happened successfully.
Please let me know how to fix this issue. I have also tried with JOOQ version 3.14.15. But no luck
When I set up a connection for Subsonic 3.0.0.4 to connect to an Oledb sql provider using the T4 Templates I get the following error: Keyword not supported 'provider' Can Subsonic access a database using OleDb? If so. How?
Which dbms do you want to use?
Since SubSonic 3 uses System.Data.Common for accessing data, it should be possible to use it with every dbms that supports ADO.net (I belive there is a OleDbProvider for ado).
But if you use a DBMS that is not supported by subsonic you have write your own DataProvider and an OleDb.ttinclude template file.
The beste starting point is to look at an existing provider:
https://github.com/subsonic/SubSonic-3.0/tree/master/SubSonic.Core/DataProviders/MySQL
https://github.com/subsonic/SubSonic-3.0-Templates/tree/master/TemplateProviders
Creating your own Provider shouldn't be to hard at all. I would use a Copy&Paste approach from an existing provider and modify everything that causes some errors.
I would use the standard SQL to LINQ Entity spaces but I have to connect to a database for a client through their application server's specific OLEDB provider. Apparently it's doing extra work after the standard OLEDB SQL commands are sent to the server. So LINQ as far as I understand is out. I built my own CRUD classes, but it's a pain doing it this way. I just want a tool that can build the standard classed so I don't have to create the layer myself.
It's MS SQL Server 2005 on the other end.
Does Subsonic work with Advantage Database server and if so are there any TT files to generate the necessary code
From the docs:
Subsonic 2.2 Currently supports 5 main database engines:
SQL Server (2000 through 2008)
MySQL (5.0+) with special support for InnoDB
Oracle - although we've had reports of some issues with Foreign Keys and Stored Procedures
SQL CE (Compact Edition)
SQLite
SubSonic 3.0 supports and has templates for:
SQL Server (2000-2008)
MySQL (5.0 +)
SQLite
Oracle support is currently in development - you can get the latest version of the templates from github. Please post details of any issues or questions to the SubSonic google group.
So in short unfortunately the answer is no.
Can I use sql express to run WSS on windows server 2008 and if I can would this be a wise move?
Have a read of this article. You can use Windows Internal Database that's built into Windows 2008 as your database server.
The primary limitation is that SharePoint's application, web front end, and database roles all have to be installed on a single server. As usage of SharePoint increases, this could become a performance bottleneck. It's also not easy to move to a farm deployment - you would have to use SharePoint backup, reinstall SharePoint in a farm role, then restore your SharePoint data.
On the other hand, it's very quick to get up and running. There are also no database size limitations (a previously common misconception). You can use SQL Server Management Studio Express to manage the databases.
I can't give you a definitive answer, but here's something that happened to me once. I once installed Team Foundation Server on a Virtual Machine, and forgot to install SQL Server first. I expected the install to fail, but let it go, just in case.
It turns out that it installed SQL Server Express, and seemed reasonably happy with the decision. I don't think it got Reporting Services and such, but it seemed happy enough.
Go over to technet.microsoft.com and find the system requirements and install documentation for WSS. See if this is a valid configuration and what the issues might be.
Can someone confirm one way or the other if SubSonic 3.0's SimpleRepository supports SQL Server CE (Compact Edition)? I tried it and failed but I'm not sure if I'm doing something wrong or if it's not supposed to work.
I'm finding conflicting information online. The SubSonic documentation page says that SQL Server CE is supported in SubSonic 3.0. However this (fairly recent) Stack Overflow question says that it isn't supported
So which is it? If it is supposed to work, does anyone happen to have a pointer to some working code so I can figure out what I'm doing wrong? Thanks!
We use System.Data.Common and from what I understand SQLCE understands System.Data.Common - you just have to be sure you specify that driver in your connection string (and I don't know what that is).
We don't have any T4's built for it yet, but for SimpleQuery it should "just work". What's the error?