[GRASSLIST:787] Re: v.in.ogr questions.

[mdeneen at japple.org]

Maybe I will sit down and create my postgres tables now.  I've been 
avoiding it to keep things simpler.

-M

On Tue, 22 Jul 2003, Radim Blazek wrote:

> On Monday 21 July 2003 21:23, mdeneen at japple.org wrote:
> > Some of my data has \n characters in it.  This makes the import fail
> > because the sql is broken into lines.
> >
> > Can someone show me what file I have to change?
> >
> > I think it should be wherever db_set_string is defined?
> 
> Yes, that was a bug in dbf/shp driver (sqlp parser). I hope I have fixed that in CVS
> so that string values in SQL statements may contain '\n' (new line) characters.
> Postgres driver was always OK, because statements are parsed by server.
> 
> Radim
>