Hi, I would like to continue a discussion started here: https://www.sqlite.org/src/tktview/c25aab7e7ea55c861313
First I assume the sqlite3 shell still has the related problem (I'm using Ubuntu, so not sure if the last version has fixed it). I would like to desagree of a comment posted on the ticket: >? Different programs do different things. There might be users that depend on the current behavior. If we fix this for the OP, it could cause problems for others. So it is unclear whether or not we should do anything for this. In the way sqlite shell currently works, users have to import a very strict formatted CSV file: no comma inside quoted string values. Implementing a way to allow commas to come inside quoted string values by no means will affect the behavior of current users relying on .import. This would be backward compatible evolution. Does anyone has an counter example? Finally, I'm not sure if the contribution sent on the last post was accepted on sqlite. Was it accepted? Does it solved the problem? Thank you so much for your attention, Leonardo Leite - "Esta mensagem do SERVI?O FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa p?blica federal regida pelo disposto na Lei Federal n? 5.615, ? enviada exclusivamente a seu destinat?rio e pode conter informa??es confidenciais, protegidas por sigilo profissional. Sua utiliza??o desautorizada ? ilegal e sujeita o infrator ?s penas da lei. Se voc? a recebeu indevidamente, queira, por gentileza, reenvi?-la ao emitente, esclarecendo o equ?voco." "This message from SERVI?O FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a government company established under Brazilian law (5.615/70) -- is directed exclusively to its addressee and may contain confidential data, protected under professional secrecy rules. Its unauthorized use is illegal and may subject the transgressor to the law's penalties. If you're not the addressee, please send it back, elucidating the failure."
