Rahkonen Jukka a écrit :
> 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
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 l
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
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 q
