On Nov 9, 1:12 pm, Thomas Mueller <[email protected]>
wrote:
> Hi,
>
> but I get back this where SPECIES is upper case
>
> Yes, the identifier of this column is unquoted, and therefore
> case-insensitive and converted to uppercase. As far as I know, this is the
> ANSI-SQL standard behavior (SQL-92 and later). I understand it doesn't look
> nice (modern) to have column names are uppercase. There is a feature to
> disable this behavior, but it is experimental and not fully tested: append
> ";database_to_upper=false" to the database URL.
>
> > and all the other
> > column names have the correct case.
>
> I wouldn't say "correct" case. The identifiers are quoted and mixed case.
> The column identifiers can't be case-insensitive because they contains a
> dot.
>
> Why the inconsistency in which it converts Species to upper case but
>
> > not the other column names? What do I do so that it leaves all
> > column names as the original case?
>
> I wouldn't leave them in the original case, because that would mean you
> always need to quote them as in
>
> select "species" from ...
>
> Also is there some way to set the correct column types (the first 4
>
> > should be real) other than tediously writing out a cast for each one?
>
> You _need_ to write "real" somewhere. You can use "cast" or you can use:
>
> create table ...(x real) as select ... from csvread ...
Thanks. Thinking about sticking the select...csvread... into another
SQL statement as you have done suggests this variation:
insert into iris0 (select * from csvread('iris3.dat')
select * from iris0
where iris0 comes from a zero row data frame in R of the same form as
iris3.dat that I can upload to H2 from R using facilities I already
have.
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/h2-database?hl=en.
