On Jan 25, 2010, at 10:15 AM, NopMap wrote: > > > Hi! > > I have a question concerning Mapnik 0.7. From the releasenotes I > gathered > that there should be an improved handling of SQL errors.
Yes, in the sense that Mapnik will now throw a `mapnik::datasource_exception` if PQstatus returns an error, which could be due to a failed connection or a failed query. Previously any failed query would simple return no results and Mapnik would blissfully give you an empty map. > Now I know that I > currently have such an error (missing column) and I am about to fix > that, Great. > but I wondered about the error handling. When running mapnik from > the python > binding (generate_image.py), I do not see any errors, After fixing the above missing column, or before? If after this may be Mapnik only throwing an error due to renderd not being able to connect, or something different than a query syntax error... > when running mapnik > from C++ (rendered), there is a segmentation fault. Where, how, and when? renderd likely needs to be improved to catch the `mapnik::datasource_exception`, but it is hard to know without more info. _______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
