Hi Fran, list,<br>thank you for responding. I will regard this issue next time.<br>Is there any chance to look up specifications for using the PostGIS driver in a proper way?<br><br>Best,<br><br>Johannes<br><br><div class="gmail_quote">
2009/9/11 Francisco José Peñarrubia <span dir="ltr"><<a href="mailto:fjp@scolab.es">fjp@scolab.es</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Sorry. Field names also un upper case.<br>
<font color="#888888"><br>
Francisco José Peñarrubia escribió:<br>
</font><div><div></div><div class="h5">> Hi Johannes.<br>
><br>
> I think this issue could be related to problems about lower case - upper<br>
> case problems in our PostGIS driver. Try to do the same with some layer<br>
> with upper case name (and with a simple name).<br>
><br>
> Hope it helps.<br>
><br>
> Fran Peñarrubia<br>
> gvSIG team<br>
><br>
> Johannes Valenta escribió:<br>
><br>
>> Hi list,<br>
>><br>
>> this morning I come up with a fairly simple question (one might think).<br>
>> How do you apply a SQL restriction on a PostGIS layer while loading it?<br>
>> Searching the list via Nabble did not give any valuable results.<br>
>><br>
>> For adding a Geodb-Layer the english manual states :<br>
>> "Any alphanumeric restriction must be introduced by means of a valid<br>
>> SQL expression<br>
>> which is attached as a WHERE clause to each call to the database."<br>
>><br>
>> Using /WHERE column = 'value' / ->did not work<br>
>> Using /WHERE column = "value"/ ->did not work<br>
>> Using /WHERE table.column = 'value'/ ->did not work<br>
>> Using /WHERE table.column = "value"/ ->did not work<br>
>> Using all of the above using /where/ ->did not work<br>
>> Using all of the above skipping /WHERE/ ->did not work<br>
>> Using all of the above inserting the whole /SELECT/-Statement -> did<br>
>> not work<br>
>> Using all of the above writing /IS /instead of/ =/ -> did not work<br>
>><br>
>> What else could be a valid expression?<br>
>><br>
>> Loading the table first and filtering it afterwards by using the<br>
>> dialogue i.e.<br>
>> /column = 'value'/ ->worked perfectly<br>
>><br>
>> What do I miss?<br>
>><br>
>> Pretty clueless in the morning (some coffee might help ;-)),<br>
>><br>
>> Johannes<br>
>><br>
>><br>
>> ------------------------------------------------------------------------<br>
>><br>
>> _______________________________________________<br>
>> Gvsig_internacional mailing list<br>
>> <a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
>> <a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
>><br>
>><br>
><br>
> _______________________________________________<br>
> Gvsig_internacional mailing list<br>
> <a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
> <a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
><br>
<br>
_______________________________________________<br>
Gvsig_internacional mailing list<br>
<a href="mailto:Gvsig_internacional@listserv.gva.es">Gvsig_internacional@listserv.gva.es</a><br>
<a href="http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional" target="_blank">http://listserv.gva.es/cgi-bin/mailman/listinfo/gvsig_internacional</a><br>
</div></div></blockquote></div><br>