[postmodern-devel] using dao-class on database with column names like "addr:city"
John Morrison
john.nmi.morrison at gmail.com
Tue Jun 14 14:40:26 UTC 2011
On Tuesday 14 June 2011, rm at tuxteam.de wrote:
> Sorry, but colons aren't a avalid part of an SQL identifier.
I would be happy with any mechanism at all which would enable me to
cope with such non-conforming databases. What's the Right Thing to
do?
> This smells like open streetmap ... must have been SQL gurus that
> designed that schema :-/
Cloudmade.com produced the shapefiles (which presumably contain OSM
data - not sure of the toolchain used). I used PostGIS 2.0 and its
shp2pgsql (built from source) to put the shapefiles into PostGreSQL
9.0.4-2.
Regarding OpenStreetMap: FYI when I was using Osmosis to import OSM
data myself (into PostGIS 1.5x), I didn't see this problem as the
schema was completely different and a lot simpler. And I cannot
easily go back to Osmosis under PostGIS 2.0 as a lot of the PostGIS
function names (upon which Osmosis relies) have changed.
> This seems wrong. The symbol 'type' only causes lock-problems when you
> try to bind its function value. Are you shure you didn't:
>
> (defclass foo ()
> ((type :accessor type)))
At one point I am sure I did. Thanks for the help!!
-jm
--
--- John Morrison
--- john.nmi.morrison at gmail.com
More information about the postmodern-devel
mailing list