LLBLGen.com Forums Bugs & Issues feed

ORMQueryConstructionException when scrolling in ServerMode by BaerlinEDV

BaerlinEDV — Tue, 07 Sep 2010 07:57:15 GMT

Hello daelmo,

I adjusted the link I posted yesterday, sorry for that.

The LINQ-query causing the problem also slightly differs from the one I posted before, sorry for any inconveniences that may have caused. (That's because we're trying to break down the problems to a simple level where it still occurs. I'll post the actual query we're aiming for at the end of this post.)

The exact query to reproduce the problem is:

Code:

Dim q = From belKomm In metaData.CoBelegKommunikation _
                    Select New With { _
                        belKomm.BelegKommId _
                    }

If I use the query from the initial post (without "Select New With ..."), then the retrieved rows are actually limited to the amount of rows specified in the take()-part of the LINQ-trace

Here's the CREATE TABLE DDL for that table:

Code:

CREATE TABLE [dbo].[CO_Beleg_Kommunikation] 
(
    [Beleg_Komm_ID] [int] IDENTITY (1,1) NOT NULL, 
    [Beleg_ID] [int] NOT NULL, 
    [Status_ID] [int] NOT NULL, 
    [DatumEingereicht] [datetime] NULL, 
    [DatumLetztePruefung] [datetime] NULL, 
    [DatumEntscheidung] [datetime] NULL, 
    [Logging_ID_Aktuell] [int] NULL, 
    [KoTr_IK] [nvarchar] (9) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, 
    [Regionaldirektion_IK] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, 
    [Vorgang_Art_ID] [int] NOT NULL, 
    [Beleg_ID_Extern] [nvarchar] (50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL 
) ON [PRIMARY]
GO

Here's the trace from when the datasource is first bound to the grid:

Code:

: Initial expression to process:
value(SD.LLBLGen.Pro.LinqSupportClasses.DataSource`1[DL.EntityClasses.CoBelegKommunikationEntity]).Select(belKomm => new VB$AnonymousType_2`1(BelegKommId = belKomm.BelegKommId)).Count()
"Patientenbetreuung.vshost.exe" (Verwaltet (v4.0.30319)): "Anonymously Hosted DynamicMethods Assembly" geladen
Method Enter: CreatePagingSelectDQ
Method Enter: CreateSelectDQ
Method Enter: CreateSelectDQ
Method Enter: CreateSubQuery
Method Enter: CreateSelectDQ
Method Enter: CreateSelectDQ
Generated Sql query: 
    Query: SELECT [LPLA_1].[Beleg_Komm_ID] AS [BelegKommId] FROM [IPV].[dbo].[CO_Beleg_Kommunikation]  [LPLA_1]  
Method Exit: CreateSelectDQ
Method Exit: CreateSubQuery
Generated Sql query: 
    Query: SELECT TOP(@p2) COUNT(*) AS [LPAV_] FROM (SELECT [LPLA_1].[Beleg_Komm_ID] AS [BelegKommId] FROM [IPV].[dbo].[CO_Beleg_Kommunikation]  [LPLA_1]  ) [LPA_L1]
    Parameter: @p2 : Int64. Length: 0. Precision: 0. Scale: 0. Direction: Input. Value: 1.
Method Exit: CreateSelectDQ
Method Exit: CreatePagingSelectDQ: no paging.
: Initial expression to process:
value(SD.LLBLGen.Pro.LinqSupportClasses.DataSource`1[DL.EntityClasses.CoBelegKommunikationEntity]).Select(belKomm => new VB$AnonymousType_2`1(BelegKommId = belKomm.BelegKommId)).OrderBy(Param_0 => Param_0.BelegKommId).Take(128)
Method Enter: CreatePagingSelectDQ
Method Enter: CreateSelectDQ
Method Enter: CreateSelectDQ
Method Enter: CreateSubQuery
Method Enter: CreateSelectDQ
Method Enter: CreateSelectDQ
Generated Sql query: 
    Query: SELECT [LPLA_1].[Beleg_Komm_ID] AS [BelegKommId] FROM [IPV].[dbo].[CO_Beleg_Kommunikation]  [LPLA_1]  
Method Exit: CreateSelectDQ
Method Exit: CreateSubQuery
Generated Sql query: 
    Query: SELECT [LPA_L1].[BelegKommId] FROM (SELECT [LPLA_1].[Beleg_Komm_ID] AS [BelegKommId] FROM [IPV].[dbo].[CO_Beleg_Kommunikation]  [LPLA_1]  ) [LPA_L1] ORDER BY [LPA_L1].[BelegKommId] ASC
Method Exit: CreateSelectDQ
Method Exit: CreatePagingSelectDQ: no paging.

As stated before, the query to reproduce the problem is just a small part of the one we're actually trying to get to work.
The full query at that time is this one:

Code:

Dim q = From belKomm In metaData.CoBelegKommunikation _
                        Join bel In metaData.BgBeleg On belKomm.BelegId Equals bel.BelegId _
                        Join sta In metaData.CoHStatusBelegKommunikation On belKomm.StatusId Equals sta.StatusId _
                        Join vart In metaData.CoHVorgangArt On belKomm.VorgangArtId Equals vart.VorgangArtId _
                        Select New With { _
                            belKomm.BelegKommId, _
                            belKomm.BelegId, _
                            bel.Belegnummer, _
                            bel.Belegdatum, _
                            belKomm.StatusId, _
                            sta.Bezeichnung, _
                            belKomm.DatumEingereicht, _
                            belKomm.DatumLetztePruefung, _
                            belKomm.DatumEntscheidung, _
                            belKomm.KoTrIk, _
                            belKomm.RegionaldirektionIk, _
                            vart.VorgangArtBezeichnung, _
                            belKomm.LoggingIdAktuell _
                        }

If I missed any information out, please let me know, and I'll try to update this as soon as possible.

Best regards,
Philipp

ORMQueryConstructionException when scrolling in ServerMode by daelmo

daelmo — Tue, 07 Sep 2010 02:29:43 GMT

BaerlinEDV wrote:

(I linked this thread in the other thread, so I'll post the link here, too, just that everyone knows what's going on:
http://beta.devexpress.com/Support/Center/Issues/EditIssue.aspx?issueid=Q273129
I'll update this thread wheather what I described above is confirmed or not.)

The link is for edit the issue. Please post the link to view the issue.

BaerlinEDV wrote:

What bothered us when looking at the traces is, that when comparing the LINQ-tracing-output to the SQL-output and the SQL Server Profiler-output. In LINQ (tracing level 3) a "take(128)"-select is being generated, but on the SQL Server Profiler and in the SQL-output (tracing level 4) the rows requested from the server don't seem to be limited to 128. The dynamic behaviour between the Grid in ServerMode and the LINQ-query make it really hard to confirm the count of rows that are being requested from the server; is there any preferred way to ensure that when the Grid and the datasource are initialized completely, only a certain amount of rows were fetched until that point of time? (Trying to display the rows via the VS results ended up in another SELECT on the SQL-Server, so that doesn't really us here.)

So the generated code in LLBLGen tracing and SQL profiler doesn't reflect the LIMIT. This could be due to the type of some fields on your entity. Please post the CREATE TABLE DDL for that table.

ORMQueryConstructionException when scrolling in ServerMode by BaerlinEDV

BaerlinEDV — Mon, 06 Sep 2010 14:59:06 GMT

Hi daelmo,

thanks for that hint. I posted a request in the corresponding Support Center of DevExpress and there indeed is a way to disable skipping and force take instead.
After studying the traces, just like you suggested, it seems like the Grid first tries to use skipping, and switches to take instead if skipping fails.
(I linked this thread in the other thread, so I'll post the link here, too, just that everyone knows what's going on:
http://www.devexpress.com/Support/Center/p/Q273129.aspx
I'll update this thread wheather what I described above is confirmed or not.)

What bothered us when looking at the traces is, that when comparing the LINQ-tracing-output to the SQL-output and the SQL Server Profiler-output. In LINQ (tracing level 3) a "take(128)"-select is being generated, but on the SQL Server Profiler and in the SQL-output (tracing level 4) the rows requested from the server don't seem to be limited to 128. The dynamic behaviour between the Grid in ServerMode and the LINQ-query make it really hard to confirm the count of rows that are being requested from the server; is there any preferred way to ensure that when the Grid and the datasource are initialized completely, only a certain amount of rows were fetched until that point of time? (Trying to display the rows via the VS results ended up in another SELECT on the SQL-Server, so that doesn't really us here.)

Edit: Corrected the link posted

Typeconverters not loading by Otis

Otis — Mon, 06 Sep 2010 12:00:53 GMT

In the next build, we'll include a specific small .exe for this: LLBLGenPro_NET40.exe. This small .exe is build against .net 4 and will enforce the designer to run on .net 4.0. We use the similar trick as with running the designer as 32bit app on a 64bit OS. We'll also add a section to the documentation illustrating this.

We decided not to add an installer thingy for this, because you might switch to .net 4 after you've installed plus writing the page for the installer was a cumbersome exercise, so we opted for this instead.

Missing field in v3 by Otis

Otis — Mon, 06 Sep 2010 07:56:29 GMT

It would be best if you attached the project file and pointed out which relationship etc. it's about. If you want to keep it hidden, please open a helpdesk thread and attach it there (please refer to this thread there for clarity )

Missing field in v3 by JMitchell

JMitchell — Mon, 06 Sep 2010 07:55:02 GMT

That's right. The FK field in Invoice exists, you can see it in the project explorer but it, and the relationship, aren't in the Catalog Explorer

GetEnumerator not found on foreach in MVC app. by daelmo

daelmo — Mon, 06 Sep 2010 02:25:07 GMT

I can't reproduce your problem. I successfully made a Northwind MVC app using LLBLGen v3.
Please generate the code again, this time in an empty folder and try again. I suspect there is something wrong in your old folders (maybe old files or something like that).

If you can't resolve it, please post more information that help us to reproduce the problem. Maybe a tiny repro application that reproduces the problem would be helpful.

LLBLGen 2.6 Final and Visual Studio 2008 by BB

BB — Fri, 03 Sep 2010 21:39:02 GMT

That seems to have fixed the problems with the checkbox, it will take me a little longer to verify that the SelectParameter is working now.

GetEnumerator not found on foreach in MVC app. by quentinjs

quentinjs — Fri, 03 Sep 2010 19:08:53 GMT

It turns out I had not resolved myearlier problem. I am using MVC and am getting this error, this used to work last year, and I've checked all my reference versions since I've moved to LLBL V3.

Quote:

Error 1 foreach statement cannot operate on variables of type 'object' because 'object' does not contain a public definition for 'GetEnumerator' c:\Projects\glossary-mvc\Index.aspx

for reference the index.aspx line in question is this

Code:

    <% foreach (var item in Model) { %>

and I have done a google on this and I have the MVC ASPX page set up correctly as follows:

Code:

<%@ Page Title="" 
    Language="C#" 
    MasterPageFile="~/Views/Shared/Site.Master" 
    Inherits="System.Web.Mvc.ViewPage<IEnumerable<glossaryDB.EntityClasses.AssociationTypeEntity>>"
%>

So I went looking for the GetEnumerator for my EntityClass and I can't see one, was this removed in V3 or moved?

Suggestions ?

Missing field in v3 by Otis

Otis — Fri, 03 Sep 2010 16:05:03 GMT

So i.o.w. there's no FK field in Invoice for this relationship? It should have an FK field for the relationship. (it should have been added automatically).