Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Jiří Činčura
You should use @p0 instead of {0} (https://msdn.microsoft.com/en-us/library/system.data.entity.dbset.sqlquery%28v=vs.113%29.aspx). Optionally you can also specify the Size in FbParameter. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ On Tue, May 2, 2017, at 09:58, Nikolaus Kern wrote: >

[Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Nikolaus Kern
Hello, I am using following query to get all workitems for a specific organisation unit: ppaQuery = "SELECT * FROM LPP_PRODUKTIONSAUFTRAEGE WHERE PRODUKTIONSSTATUS NOT IN ('Abgeschlossen','Storno') ORDER BY PRODUKTIONSAUFTRAG_ID"; tmpPPA =

Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Nikolaus Kern
Hi, I just saw that the query and the execution do not match correct. This is the query with the parameter that creates an exception if the parameter is "Halle 6 - Schlosserei". ppaQuery = "SELECT * FROM LPP_PRODUKTIONSAUFTRAEGE WHERE PRODUKTIONSSTATUS NOT IN ('Abgeschlossen','Storno') AND

Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Jiří Činčura
> Can you please add 1 line to describe the difference between using {0} > vs. @p0 ? Well, AFAIK only the @p0 is supported. Maybe the {0} works as well, but I know only about the @p0 from documentation. Of course we can check EF6 sources, but I'm too lazy to do that. :D -- Mgr. Jiří Činčura

Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Jiří Činčura
What's the AUSLASTUNG_GEHOERT_ZU's datatype? -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ On Tue, May 2, 2017, at 11:55, Nikolaus Kern wrote: > Hello Jiri, > > thanks for the response. > > I guess I am missing something here. The code below produces the same > error as {0}. > >

Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Nikolaus Kern
Hello Jiri, thanks for the response. I guess I am missing something here. The code below produces the same error as {0}. ppaQuery = "SELECT * FROM LPP_PRODUKTIONSAUFTRAEGE WHERE PRODUKTIONSSTATUS NOT IN ('Abgeschlossen','Storno') AND AUSLASTUNG_GEHOERT_ZU = @p0 ORDER BY

Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Nikolaus Kern
Hello Jiri, its my fault: AUSLASTUNG_GEHOERT_ZU is Varchar(20), the parameter "Halle 6 - Schlosserei" is 21 chars long After correcting the length to 30 it works fine. Interessting the slq console does not compain about the too long input for the query. Thanks for answering to my posting

Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Daniel Rail
Hi, At May 2, 2017, 7:55 AM, Jiří Činčura wrote: >> Can you please add 1 line to describe the difference between using {0} >> vs. @p0 ? > Well, AFAIK only the @p0 is supported. Maybe the {0} works as well, but > I know only about the @p0 from documentation. Of course we can check EF6 >

Re: [Firebird-net-provider] Problem creating the code with EF6 Code First from Database

2017-05-02 Thread Daniel Rail
Hi, At April 24, 2017, 12:39 PM, Jiří Činčura wrote: >> But, what could cause it not to recognize those fields properly? >> Because when I look in the database's system tables, the >> RDB$FIELD_TYPE and RDB$FIELD_LENGTH both have values in them, one >> would be

Re: [Firebird-net-provider] EF handling - as string parameter

2017-05-02 Thread Jiří Činčura
What parameter? I don't see any parameter in the query. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!