Use subsonic 3.0 SimpleRepository to a existing database

subsonicsubsonic3

I want to use subsonic 3.0 SimpleRepository in my project, but there is a problem :

If my table's name like Product etc. then I can't get any data from database,
because subsonic generate the sql statement like "Select * from Products ..."

PS: I don't want to change my table name.

I wrote a t4 template to solve this problem, I hope someone can take a look at my
code and tell me am i do the right thing?

Code: SimpleRepositoryDemo

Best Answer

It sounds like you already have a database designed in which case I would suggest you use the LinqTemplates or ActiveRecord instead. SimpleRepository seems to really be suited to a code first development process rather than a database first.

Related Solutions

Sql – Subsonic – How to use SQL Schema / Owner name as part of the namespace

I was going to suggest the multiple provider approach too. But a lot of the plumbing is already in subsonic for ownership. If you edit a couple of lines in CS_ClassTemplate.aspx you can create a namespace for each owner profile. Change around line 58 (I'm using v2.1) to

namespace <%=provider.GeneratedNamespace%><%=owner%>

where owner is

string owner = "." + tbl.SchemaName;
if(owner == ".dbo")
  owner = "";

You put that up above, around line 14. This way you can have a namespace for every owner like: Northwind.Suppliers, Northwind.Customers, etc. I left dbo as just Northwind so all the tests would compile without a lot of editing. I ran a simple select query and I think it will work the way you want.

R – Defining SubSonic 3 ActiveRecord migrations

You can still use SubSonic 3 as a DAL and let SubSonic 2.2 generate the migrations for you. You just need sonic.exe and it's dependencies to execute the migration files.

To be more precise, I have folder Migrations in my DataLayer Project, that keeps all the migration Files but set the BuildAction to none. So I have Syntax Highlighting (but no error checking unless I set BuildAction back to compile) but the code does not mess my project.

You can keep them in an own project, of course. But I like it this way to have it under version control and be sure that my current DAL is matching my migration version.

In addition, I have named my config file migration.config (instead of app.config/web.config) and use this commandline to execute my migrations.

Command:           /path/to/sonic.exe  
Arguments:         migrate /config migration.config
Working Directory: $(SolutionDir)MyProject.Datalayer

Notice the /config switch to override the config file sonic.exe is looking for.

Best Answer

Related Solutions

Sql – Subsonic – How to use SQL Schema / Owner name as part of the namespace

R – Defining SubSonic 3 ActiveRecord migrations

Related Topic