example shows 0s, instead of the inserted data

[spytheman]

Running the example produces 0, instead of the inserted values:

import elliotchance.vsql.vsql

fn main() {
	mut db := vsql.open('/tmp/test.vsql') ?

	// All SQL commands use query():
	db.query('CREATE TABLE foo (a FLOAT)') ?
	db.query('INSERT INTO foo (a) VALUES (1.23)') ?
	db.query('INSERT INTO foo (a) VALUES (4.56)') ?

	// Iterate through a result:
	result := db.query('SELECT * FROM foo') ?
	for row in result {
		println(row.get_f64('a'))
	}

	// See SQLSTATE (Errors) below for more examples.
}

The values are inside the /tmp/test.vsql as validated by running the vsql-cli.v later.

[spytheman]

If I change the loop to do println(row), I get:

elliotchance.vsql.vsql.Row{
    offset: 58
    data: {'A': elliotchance.vsql.vsql.Value{
        typ: FLOAT
        f64_value: 1.23
        string_value: ''
    }}
}
elliotchance.vsql.vsql.Row{
    offset: 78
    data: {'A': elliotchance.vsql.vsql.Value{
        typ: FLOAT
        f64_value: 4.56
        string_value: ''
    }}
}

so the data is there, but perhaps .get_f64() can not access it 🤔

[spytheman]

println(row.get_f64('A')) shows the values

[elliotchance]

Ah yes, sorry. In a recent update (v0.2.4 - #6) to conform to the SQL standard, all regular (non-delimited) identifiers are represented in upper case. I forgot to update the example to be row.get_f64('A').

That Row actually needs some love. It should return an error with a helpful message instead of returning a misleading value:

println(row.get_f64('Foo') ?)
// no such column Foo, did you mean FOO?

Alternatively, CREATE TABLE foo ("a" FLOAT) would allow you to use row.get_f64('a').

[spytheman]

imho returning a helpful error is better - code is written just once, and the error will be caught in development; forcing get_f64 functions to upcase their arguments will happen in production too