Thanks for this great extension.
It works smoothly with 500Mo files.
And it's a workaround to some shortcomings of the '.import' command:
- no need to create a table before,
- no need to delete the header row before/after,
- no error if the number of columns is not homogeneous,
- ...
It's a nightmare to work with the CSV format but I have to.
I made a quick and dirty fix to the USE_HEADER_ROW mode to replace
whitespaces, slashes or hyphens by underscores.
But I look for a better solution. Is there any way to make sure a string is
a valid column name?
Regards
On Mon Apr 19 17:32:13 GMT 2010, Shane Harrelson <shane at sqlite.org>
wrote:
> Thanks for the report. The extension is still very a much a
> work-in-progress and any feedback is greatly appreciated.
>
> -Shane
>
>
> On Sun, Apr 18, 2010 at 12:51 PM, gwenn <gwenn.kahz at gmail.com> wrote:
> > Hello,
> > There is a little bug/typo in the csv extension when lines exceed 100
> > characters:
> > *** glibc detected *** sqlite3: realloc(): invalid pointer:
> > 0x0000000000ad1a78 ***
> > ======= Backtrace: =========
> > /lib/libc.so.6[0x7f6dab009d16]
> > /lib/libc.so.6(realloc+0x321)[0x7f6dab00fda1]
> > ./libSqliteCsv.so[0x7f6da9ef9dbf]
> >
> > A possible patch is:
> > --- /tmp/SQLite-d474195a997b9d94/ext/csv/csv.c 2009-11-05
05:14:30.000000000
> > +0100
> > +++ csv.c 2010-04-18 18:48:04.000000000 +0200
> > @@ -160,7 +160,7 @@
> > }
> > }
> > if( bShrink ){
> > - pCSV->zRow = realloc( pCSV->zRow, n+1 );
> > + pCSV->zRow = sqlite3_realloc( pCSV->zRow, n+1 );
> > pCSV->maxRow = n+1;
> > }
> > return bEol ? pCSV->zRow : 0;
> >
> > Regards.
> > _______________________________________________
> > sqlite-users mailing list
> > sqlite-users at sqlite.org
> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
> >
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
