Is the code gen tool sqlmetal only a mapper to linq to sql?
I'm looking for something that will create common CRUD operations also like:
GetUserByID
UpdateUserByID
InsertUser
GetAllUsers
etc.
SQLmetal, is it only a mapper for linq to sql
sqlmetal
Related Solutions
SQLMetal is fine for generating the model classes. I am not very fond of the LINQ designer, so typically, I will use the designer in the initial design phase, and later additions or alterations to the datamodel is then done by hand editing the dbml file.
I use this simple command for building my LINQ-to-SQL classes, which I put in a batch file for maximum convenience:
sqlmetal /code:YourCodeFile.designer.cs /namespace:Desired.Namespace YourModel.dbml
The SQLMetal approach works fine for me, and is a reliable way of generating the code. Any handwritten additions to the generated classes, should of course be kept in partial class declarations in a separate code file.
The answer to your title question is yes it is a fine solution for database with tables only (and to a point can grow when your database grows to include other database constructs like views and stored procedures).
- Pretty shallow. The main difference you'll find is that certain methods that work on Linq2Objects don't work for Linq2SQL. You have to be careful when mixing objects and Linq2SQL together. You'll know you hit this when you get an exception saying something to the effect of "The only thing we support is Contains".
- Quite.
- You'll probably find that in certain situations Linq2SQL doesn't generate the most efficient SQL.
- Sometimes things can get tricky with transactions.
- There is no update statement. Every time you want to update a set of records you have to select them, update each one and then
SubmitChanges(). - Unless you're only doing selects you need to have a primary key on your table. Without a primary key you can't delete or update.
- Linq2SQL doesn't directly support many-to-many relationships.
- A simple solution would be to setup a prebuild task that generates your Linq2SQL DataContexts every time you build.
As to your goal of using Linq2SQL for everything, be ready for some nasty LINQ queries (and nasty debugging cycles). The join syntax is verbose and depending on the complexity of your queries can quickly become harder to maintain than the SQL equivalent. Grouping isn't as easy as GROUP BY.
Best Answer
Yeah, SQLMetal only creates the mapping file. Most CRUD operations are trivial, though, once you've set up the mappings in LINQ to SQL. Generally, you wouldn't code with methods like this when using LINQ to SQL... For example, GetUserByID would just be:
Seems more verbose for really trivial operations, but once you do more complex operations, it gets really powerful, really fast.