LLBLGen.com Forums Generated code feed

StoredProcedure T imeout in v3 by JMitchell

JMitchell — Tue, 07 Sep 2010 09:25:14 GMT

That's great, Thanks for your help. Much appreciated (I assume this fix will be in the next relese?)

StoredProcedure T imeout in v3 by Otis

Otis — Tue, 07 Sep 2010 09:15:16 GMT

Please see the attached dll for the fix.

Adapter doesn't have this problem btw, it's only Selfservicing, and also only stored procs. Normal commands do get the timeout set.

StoredProcedure T imeout in v3 by Otis

Otis — Tue, 07 Sep 2010 08:42:03 GMT

Reproduced. Looking into it.

(edit) bug, timeout isn't set for a proc call. Working on fix. The reason it's not set is because the proc is not a SQL command created by the DQE. The timeout is set on the DQE, and the proc call is not called as a generated query, but directly, so the parameter isn't set.

Predicate Expression out of sync by yogesh_shtty

yogesh_shtty — Tue, 07 Sep 2010 04:01:21 GMT

daelmo wrote:

The logical explanation is that no rows in your DB match your filter expression. If no rows are returned, the entity is marked as OutOfSync. So maybe you should check the entityFields.State or the entity.IsNew property to know if the entity was already fetched and you can read values. The same applies to debugging. If you try to access properties of a non-existent entity (fetched but not existent = out of sync) you will get that error.

Hi Daemo. Exactly. I am trying to see whether value exists in DB or not. I am using return (accountnature.Fields.State) == EntityState.Fetched; as mentioned by you.

If this is how it works I mean out of sync is what it gives and still it works ! then am ok wid it

Predicate Expression out of sync by daelmo

daelmo — Tue, 07 Sep 2010 02:09:59 GMT

StoredProcedure T imeout in v3 by Otis

Otis — Mon, 06 Sep 2010 15:44:14 GMT

JMitchell wrote:

No worries. The stored procedure wasn't in the generated code previously, which is why I used, DbUtils.CallRetrievalStoredProcedure. It is now. The actual name is AirPlusInvoiceMismatchFilter - I often trim things to aid readability - didn't realise you'd be looking at the attachment on the other thread!

That was the easiest way to look how the proc was setup in your vb.net code

We'll look into it.

StoredProcedure T imeout in v3 by JMitchell

JMitchell — Mon, 06 Sep 2010 15:42:31 GMT

StoredProcedure T imeout in v3 by Otis

Otis — Mon, 06 Sep 2010 15:37:23 GMT

I used your project from the other thread, generated code and didn't see the method you refer to in your code, so additionally to what you said: "I was previously using DbUtils.CallRetrievalStoredProcedure but since that doesn't exists now", we concluded that you defined a custom stored procedure call in code which is now outdated / doesn't follow the code path set up for stored procs in v3.

As this is an assumption, could you please tell us why you said "I was previously using DbUtils.CallRetrievalStoredProcedure but since that doesn't exists now" ? Is the proc you refer to in your post a generated proc call or a method call you added yourself? If you defined it yourself, you have to rewrite it to follow the pattern we use in the generated code now for calling stored procedures. (it's really simple, see the generated retrievalprocedures class).

If the proc is generated, then our assumption is wrong and we'll look into whether everything is indeed wired up correctly. Sorry for the confusion

Predicate Expression out of sync by yogesh_shtty

yogesh_shtty — Mon, 06 Sep 2010 14:19:58 GMT

I have also attached out of sync error image which shows only the folllowing line in stack trace

at SD.LLBLGen.Pro.ORMSupportClasses.EntityBase2.GetValue(Int32 fieldIndex, Boolean returnDefaultIfNull) in c:\Myprojects\VS.NET Projects\LLBLGen Pro v3.0\Frameworks\LLBLGen Pro\RuntimeLibraries\ORMSupportClasses\AdapterSpecific\EntityBase2.cs:line 2501
at ClubCentricHelper.EntityClasses.CountryEntity.get_Modifieddate() in D:\ProjectLive\LLBLGen Pro Projects\DatabaseGeneric\EntityClasses\CountryEntity.cs:line 702

Predicate Expression out of sync by yogesh_shtty

yogesh_shtty — Mon, 06 Sep 2010 14:09:49 GMT

Walaa wrote:

The error in the screenshot is logical: the 'Field' property is selfservicing specific, you should check the 'FieldCore' property.

Dont see any error there how ever attached screen shot. But my outofsync remains though am fetching entity afer save