Hi there,
I have question/suggestion about that method. When it goes though the loop it
calls the driver's CreateField several times, depending on the number of
columns on the table. In a DBMS environment, at that point the table is already
created and the only thing the driver's CreateField() can do is to issue some
ALTER TABLE statements. But that is too time consuming. It takes more time than
to load geometry in some cases.
Is there a way to pass the field description information to the driver and let
it decide to create the table at once with a complete description of the fields?
Best regards,
Ivan
_______________________________________________
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
