Thomas, Took a look at the source and it is pretty straightforward. Changed/added four or five lines and it seems to be working fine.
Understand why you don't want to change the behaviour since it would almost certainly break existing stuff and as you say add complication to an already messy situation. The messiness I'm referring to is lack of any decent CSV standardization, not H2. Thanks. On Thursday, October 3, 2013 5:59:43 PM UTC-4, WillyMac wrote: > > I would expect that the only representation for null would be the one > specified. Maybe it is intended to work this way, but I find it confusing > to have two null representations. Why bother specifying null=xxx if ,, is > read as null anyway? > > Or maybe my syntax is wrong? > > *Input file:* > > c1,c2,c3 > a,,c > a,"",c > a,XX_null_XX,c > > *SQL:* > > select * from > csvread( 'tst.csv', null, 'null=XX_null_XX' ) > > *Output (? == null):* > > C1 C2 C3 > ----------------- ----------------- ----------------- > a ? c > a c > a ? c > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/groups/opt_out.
