[prev in list] [next in list] [prev in thread] [next in thread] 

List:       fdo-users
Subject:    RE: [fdo-users] Re: FDO 3.5 ArcSDE Provider Oracle ORA-00920
From:       Romica Dascalescu <Romica.Dascalescu () autodesk ! com>
Date:       2010-11-03 16:19:22
Message-ID: CA94CA039E46DB46AFD4E0EE8BBAE7CB0CD384 () 005-TK5MPN1-002 ! MGDADSK ! autodesk ! com
[Download RAW message or body]

Hi Henning,

I had a look at your change and it's OK, however I would propose some additional \
changes to remove class FilterAnalyzer and flags mFilterAnalyzed, mUseNesting. This \
will simplify the code and will make possible use less brackets in a filter. The same \
method is used in FDO & SQLite filter ToString in order to avoid too many brackets. I \
attached a code change (ArcSDE.patch) to the ticket \
(http://trac.osgeo.org/fdo/ticket/719). Could you please have a loot at the code \
change proposed and test it if possible and let me know your opinion?

Regards,
Romy.

________________________________________
From: fdo-users-bounces@lists.osgeo.org [fdo-users-bounces@lists.osgeo.org] on behalf \
                of maland [hma@powel.com]
Sent: Wednesday, November 03, 2010 4:34 AM
To: fdo-users@lists.osgeo.org
Subject: [fdo-users] Re: FDO 3.5 ArcSDE Provider Oracle ORA-00920

I have debugged the ArcSDE provider source and identified the problem. It
seems to be related to the "nesting" in function
ArcSDEFilterToSql::ProcessBinaryLogicalOperator. It happens when both
operands are "attribute"-style filters. The parenthesis matching is broken.
Where can I post the bugfix proposal so it can be included in the next
release?

Regards
Henning Maeland


oyvind idland wrote:
> 
> I get the same problem here.
> 
> It seems to me that the SQL generator goes a bit too far in wrapping
> everything in parenthesis ?
> 
> Unfortunately it seems that the SDE provider is currently broken.
> 
> 
> -- Oyvind
> 
> 
> On Fri, Oct 1, 2010 at 10:27 AM, maland <hma@powel.com> wrote:
> 
> > 
> > I've been able to find the SQL generated by the ArcSDEFilterToSql class,
> > and
> > there is obviously a problem with the parantheses matching. Example of
> > SQL
> > generated:
> > 
> > SELECT  XROW, YROW FROM EXAMPLE_POINTS WHERE YROW = 0  AND  ( ( ( (XROW)
> > =
> > (0)  ( OR  ( (XROW)  =  (1) ) ) )
> > 
> > Hopefully the authors of the FDO ArcSDE provider can have a look at this?
> > 
> > 
> > Regards
> > Henning
> > --
> > View this message in context:
> > http://osgeo-org.1803224.n2.nabble.com/FDO-3-5-ArcSDE-Provider-Oracle-ORA-00920-tp5587468p5590547.html
> >  Sent from the FDO Users mailing list archive at Nabble.com.
> > _______________________________________________
> > fdo-users mailing list
> > fdo-users@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/fdo-users
> > 
> 
> _______________________________________________
> fdo-users mailing list
> fdo-users@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/fdo-users
> 
> 

--
View this message in context: \
http://osgeo-org.1803224.n2.nabble.com/FDO-3-5-ArcSDE-Provider-Oracle-ORA-00920-tp5587468p5700469.html
 Sent from the FDO Users mailing list archive at Nabble.com.
_______________________________________________
fdo-users mailing list
fdo-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-users_______________________________________________
 fdo-users mailing list
fdo-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-users


[prev in list] [next in list] [prev in thread] [next in thread]