I guess more generally there is an issue with having to do a round trip through WKT to update a record - it loses precision and is there is an explicit warning about using it for passing data:
http://postgis.org/docs/ST_AsText.html I don't see any point in altering how the select represents the record (and WKT is more interpretable) but it would be better if you could pass a WKB straight back to the record. The update method avoids the problem but I think it might be fixable by updating the representer here: https://github.com/web2py/pydal/blob/master/pydal/representers/postgre.py#L22 If the first character of the value is 0 (zero) then the code could attempt to treat the value as WKB and just return the value (possibly with SRID) rather than having to put it through ST_GeomFromText(). The backend validates WKB inputs, so you can't just pass in any old nonsense starting with a zero. -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
