On 1 May 2018, at 15:20, Simon Slavin wrote:
> Seems like the best way to solve this would be to write a converter for
> Windows which converts SCSV to CSV. Then it could be used by all Excel users
> instead of just SQLite users.
As the heavy lifting of implementing Python on Windows has been
For those of you who use SQLite to prepare CSV for import/open into
Excel beware of this problem:
"Text","Next bit is a reference id","A001"
"text","same again","0009"
On Windows, In the second row, 3rd column Excel will remove the
leading zeroes, if the file has an extension of .csv
The same con
On 5/1/18, 1:42 PM, "sqlite-users on behalf of R Smith"
wrote:
My point is that CSV was not necessarily "meant" to be what you say. Who
exactly "meant" for it to be that? Because the official stuff makes no
such claim or mention.
Bah. Existential shenanigans. There's probably so
On 2018/05/01 8:21 PM, Peter Da Silva wrote:
On 5/1/18, 1:15 PM, "sqlite-users on behalf of R Smith"
wrote:
On 1 May 2018, at 6:43pm, Peter Da Silva
wrote:
> CSV is an interchange format, it's for software to communicate with other software, so the syntax needs to be indepen
On 5/1/18, 1:15 PM, "sqlite-users on behalf of R Smith"
wrote:
On 1 May 2018, at 6:43pm, Peter Da Silva
wrote:
> CSV is an interchange format, it's for software to communicate with other
software, so the syntax needs to be independent of the locale since you don't
know if the se
On 1 May 2018, at 6:43pm, Peter Da Silva wrote:
CSV is an interchange format, it's for software to communicate with other
software, so the syntax needs to be independent of the locale since you don't
know if the sender and recipient are in the same locale. Field separator is
syntax, so the l
On 1 May 2018, at 6:43pm, Peter Da Silva wrote:
> CSV is an interchange format, it's for software to communicate with other
> software, so the syntax needs to be independent of the locale since you don't
> know if the sender and recipient are in the same locale. Field separator is
> syntax, so
To another post hating on Excel - Excel has many flaws, but this is not
one of them, it's a fault of the list-separator setting in the Windows
OS on which the Excel runs.
CSV is an interchange format, it's for software to communicate with other
software, so the syntax needs to be in
On 2018/05/01 4:20 PM, Simon Slavin wrote:
On 1 May 2018, at 3:01pm, Olivier Mascia wrote:
My question was more generic, even though it didn't look that way: the well-known and (maybe too)
much-used software tool named Excel tend to encourage people to export "CSV" files which
are actually
On 1-5-2018 16:20, Simon Slavin wrote:
> On 1 May 2018, at 3:01pm, Olivier Mascia wrote:
>
>> My question was more generic, even though it didn't look that way: the
>> well-known and (maybe too) much-used software tool named Excel tend to
>> encourage people to export "CSV" files which are act
Having tried to write a generic clean HANDLES ALL CSV reader for speedtables, I
kind of want to burn Excel with nuclear fire, but that's a side issue. :)
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/c
> From: sqlite-users
> [mailto:sqlite-users-boun...@mailinglists.sqlite.org] On
> Behalf Of Olivier Mascia
>
> Considering:
>
> CREATE VIRTUAL TABLE temp.t1 USING csv(filename='thefile.csv');
>
> Is there any way to teach the csv extension to use ';'
> instead of ',' as the column delimiter,
On 1 May 2018, at 3:01pm, Olivier Mascia wrote:
> My question was more generic, even though it didn't look that way: the
> well-known and (maybe too) much-used software tool named Excel tend to
> encourage people to export "CSV" files which are actually "SCSV" files
> (semi-colon separated val
> Le 1 mai 2018 à 14:00, Simon Slavin a écrit :
>
>> CREATE VIRTUAL TABLE temp.t1 USING csv(filename='thefile.csv');
>>
>> Is there any way to teach the csv extension to use ';' instead of ',' as the
>> column delimiter, getting away from the strict RFC4180 definition?
>
> The source code for
On 1 May 2018, at 11:11am, Olivier Mascia wrote:
> CREATE VIRTUAL TABLE temp.t1 USING csv(filename='thefile.csv');
>
> Is there any way to teach the csv extension to use ';' instead of ',' as the
> column delimiter, getting away from the strict RFC4180 definition?
The source code for the csv e
Considering:
CREATE VIRTUAL TABLE temp.t1 USING csv(filename='thefile.csv');
Is there any way to teach the csv extension to use ';' instead of ',' as the
column delimiter, getting away from the strict RFC4180 definition?
--
Best Regards, Meilleures salutations, Met vriendelijke groeten,
Olivie
16 matches
Mail list logo