[Gvsig_english] gvSIG 1.1.2 applying SQL restriction on PostGIS layer while loading

[Francisco José Peñarrubia]

Hi Johannes.

No, sorry. Just to look into source code.... :-(.

Anyway, the driver will change totally in 2.0 release.

Thanks for your time.

Fran.

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