Hi, One thing came into my mind. The layer created by the database query seems to get the whole query string as its name. In my yesterdays case the query was rather long with a list in "AND attrib in (value1, value2...)" clause. I wouldn't be surprised if something like 7000 character long layer name has some side effects.
-Jukka- Larry Becker wrote: So if the DB Query PlugIn loads results into memory, it should work fine with tools that iterate through the entire layer. This still leaves the question of what happens when you do this to a DataStore layer that loads only the current view into memory. This may depend on the implementation. For the PostGIS driver in JUMP, iterating will probably execute a next() on the current ResultSet, which I believe will just step though the features in the current view. Unless someone can shed additional light on this issue, I would recommend against using tools that work on entire layers (like Auto Assign Attributes) in conjunction with database backed datasets, unless you first zoom to the extent to ensure they are all in RAM. Of course, if you can't write the result back to the database, there isn't much point in doing this anyway. regards, Larry On Tue, Apr 7, 2009 at 4:11 AM, Rahkonen Jukka <jukka.rahko...@mmmtike.fi>wrote: > Hi, > > DB Query plugin sends full SQL query to Oracle (or PostGIS) from the input > window. Nice tool indeed because query can contain joins, and if the > resulting lines do not have geometry a default geometry is created so that > it can still be opened by OJ. Therefore pure attribute tables can also be > queried with OpenJUMP. Spatial queries naturally work as well if someone has > nerves to write them into input box. > > Actually I had not really worked with these layers before, I use the tool > for visualizing Oracle data and converting to shapefiles. Editing does not > make sense often because results cannot be written back to Oracle. I came to > this because I had to add X and Y coordinates as attributes and I was > remembering that there was some nice new tool introduced just for this > purpose and I tried everything I found from the menu. > > Unfortunately I cannot repeat the error today. All the tools, inluding Auto > Assign Attribute work just perfectly :( > > -Jukka Rahkonen- > > ------------------------------ > Larry Becker wrote: > > Jukka, > > I haven't worked with the DB Query plugin from Oracle. Does it load all > of the layer into memory or just the portion on screen? > > The only thing I can think of is that the FeatureCollection iterator > doesn't work for this dataset. Are there other OJ tools that do similar > things that work with this layer? > > Larry > > On Mon, Apr 6, 2009 at 10:20 AM, Larry Becker <becker.la...@gmail.com>wrote: > >> Hi, >> >> I'll take a look at it to see where it might be getting hung up. >> Clearly, it shouldn't lock up. >> >> Larry >> >> >> On Mon, Apr 6, 2009 at 9:53 AM, Sunburned Surveyor < >> sunburned.surve...@gmail.com> wrote: >> >>> Jukka, >>> >>> Could it be that the Auto Assign Attribute tool needs write access to >>> the layer, and the DB Query plug-in only has read access? >>> >>> SS >>> >>> On Mon, Apr 6, 2009 at 3:27 AM, Rahkonen Jukka >>> <jukka.rahko...@mmmtike.fi> wrote: >>> > Hi, >>> > >>> > It looks like Auto Assign Attribute tool jams the whole OpenJUMP if it >>> > is tried to use for a layer that is just fetched from database with >>> > database query. >>> > I made the query with DB Query plugin from Oracle. If I save the query >>> > result into shapefile and open it the Auto Assign Attribute tool works >>> > fine with this shapefile layer. >>> > >>> > Jamming means that OJ does not seem to do anything at all. It does not >>> > consume processor power nor does it give any error messages but I did >>> > not find any other way to make OJ to react than killing the process. >>> > >>> > -Jukka Rahkonen- >>> > >>> > >>> ------------------------------------------------------------------------------ >>> > _______________________________________________ >>> > Jump-pilot-devel mailing list >>> > Jump-pilot-devel@lists.sourceforge.net >>> > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> > >>> >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >> >> >> >> -- >> http://amusingprogrammer.blogspot.com/ >> > > > > -- > http://amusingprogrammer.blogspot.com/ > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > -- http://amusingprogrammer.blogspot.com/ ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
