ULinqGen Forum Rss Feed

New Post: Relationship Foreign Key Errors

gtas — Thu, 17 Dec 2009 09:08:54 GMT

I tried your generator but this don't creates the DataContext!

[EDITED]

I copied the generated DataContext from MS generator and used it in your file...Select is working.,

I'm having dificulties though with Updates and Inserts, something about the keys of my Tables.

"An attempt was made to remove a relationship between a "Table-Object" and a "Table-Object". However, one of the relationship's foreign keys ("Key") cannot be set to null." <-- it is not null though!

Any help?

New Post: T4 Templates?

benjamine — Mon, 06 Apr 2009 12:19:44 GMT

To be honest, we haven't consider using T4 templates when ULinqGen was been developed, they are a very good choice, actually they say Entity Framework is going to support T4 templates in v2.

Without having analyzed this further, the only drawback I can see of T4 templates, against the current ULinqGen implementation, which uses CodeDOM, is that CodeDOM is language independent.
Using T4 templates will force you to write a T4 template for every language you choose to support, and on future changes in the language syntax you may need to update the templates.
However T4 templates are a lot much easier to write and specially to read, than CodeDOM code.

New Post: T4 Templates?

mnurre — Wed, 22 Oct 2008 03:30:27 GMT

What would be involved to have the code generated by T4 templates to allow for easier end user customization instead of having it hard-coded?

Great project, by the way.

New Post: Insert failed when associated property is null?

mmkk — Wed, 09 Jul 2008 08:30:56 GMT

Currently I'm trying to implement LINQ to SQL with POCO way, so I use ULINQGen to help generate the POCOs, it's great for most of search requirements, but I just met a scenario like this, it's based on Northinwind in your test application:

Order_Detail od = new Order_Detail();
od.OrderId = xxx;
od.UnitPrice = 100;
//set value for other properties

DataContextInstance.Order_Details.InsertOnSubmit(od);
DataContextInstance.SubmitChanges();

this kind of codes will not work as what i expected, an exception will be throw out. And event if i tried to assign a new instance to Order_Details' Order property, DataContext somehow will also try to add new Order to database too, then an primary key conflict ocurred, that's weired. To make everything works, I need to have a nullable OrderId, but it's not a real good idea, because it brings difference between database schema and domain entity. Any comments about this?