[OSM-talk] Parametrizing SQLs /was Re: gpx import problem?
Stefan Baebler
stefan.baebler at gmail.com
Thu Sep 13 08:34:00 BST 2007
> > > Mysql::Error: Column 'tile' cannot be null: INSERT INTO gps_points
> > > (`timestamp`, `latitude`, `altitude`, `tile`, `gpx_id`, `longitude`,
> > > `trackid`) VALUES('2007-09-10T15:00:35+00:00', 42455527, 442.343872,
> > > NULL, 38444, 13926608, 1)
>
> > Hi, wouldn't using SQL parameters everywhere speed up the DB operations?
> > AFAIK modern SQL engines generally recognizes identical SQL statements
> > and can optimize things internally for most often executed stuff.
>
> 1. The above error message is not an indication of prepared statements
> not being used (as MySQL will create such messages even if they are).
I knew that, that's why i forked the mail thread.
> 2. ActiveRecord, the ORM framework used by Ruby on Rails, does not
> support prepared statements AFAIK.
Ok, I wasn't aware of this RoR/ActiveRecord shortcoming.
Tnx,
Stefan
More information about the talk
mailing list