On Thu, Mar 25, 2010 at 14:39, Marco Aurélio Castro
<mcas...@mcsoft.com.br> wrote:
> The query brought a lot of fields that I didn’t asked for and the OUTER APPLY
> part of the code don’t works. The message is:
The columns are not on my side of playground. EF selects what it
needs. The outer apply right now doesn't work with Firebird as it's
not supported. Thought there's surely way to rewrite the query inside
the provider, it's way harder than let developer rewrite the
originating query. I know it's pity, but it's all about available
resources... :(
> Well, I hope this explanations drives you to a better provider implementation.
I'm not sure, whether the query was wrongly translated by provider
(the translation in our provider isn't changing the query in any way)
or EF is simply generating something you're not expecting and think
it's wrong. Any way can you compare the results with SqlClient?
--
Jiri {x2} Cincura (x2develop.com founder)
http://blog.cincura.net/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
