hello there

re your Firebird & LINQ code...

First of all, please forgive me if my questions here seem somewhat naive, but I am a beginner where LINQ is concerned...

I don't understand the impact of your using LINQ on the end user. As far as I was aware, the beauty of LLBLGen is that it generates the data access code and entities for me at the click of a button. So why should I care whether you do this using LINQ or more traditional mappings under the hood?

Or are we saying that the LINQ code will be exposed to me at a higher level. So that instead of using the predicates etc. to do joins I can now handle this logic in the more familiar LINQ logic?

I am just trying to get my ahead around how LINQ in LLBLGen will benefit me. LINQ is a technology that I am quite excited about so I am really keen to understand how it affects my usage of LLBLGen.

Many thanks for any clarifications.

weebubba wrote:

So why should I care whether you do this using LINQ or more traditional mappings under the hood?

I think the implementation of LINQ is an extension on top of what they already have (if I am not mistaken). So, to use your analogy, this is more like a steering wheel rather than "under the hood".

weebubba wrote:

Or are we saying that the LINQ code will be exposed to me at a higher level. So that instead of using the predicates etc. to do joins I can now handle this logic in the more familiar LINQ logic?

Yes, and might I add that it is A LOT shorter than using predictaes etc.

weebubba wrote:

I am just trying to get my ahead around how LINQ in LLBLGen will benefit me. LINQ is a technology that I am quite excited about so I am really keen to understand how it affects my usage of LLBLGen.

All in all, it doesnt have to change the way you use LLBLGen at all. I have enjoyed using it because of my ability to more easily create dificult queries without the verbosity of the (well built) predicate system afforded in the standard stuff.

And I will add the following and best part about it: The MS stuff ONLY works for SQL Server. What we have here should also work with Firebird.

Or are we saying that the LINQ code will be exposed to me at a higher level. So that instead of using the predicates etc. to do joins I can now handle this logic in the more familiar LINQ logic?

Exactly, so now you have more choices of how to write the predicates

ABout firebird: The linq queries create derived tables in a lot of cases. Firebird 1.x doesn't support derived tables. So if you're going to use Linq, be sure you're using Firebird 2.x