SQL Statement (wrapper statement)

[the-moisrex]

• [x] bind
• [x] support stmt[index] = value syntax (binding?)
• [x] support int val = stmt[index] (column retrieval)
• [x] execute (or step?)
• [x] Error handling
• [x] Logging
• [x] Stmt Iterator (what is it even?) (Removed it in the database class)
• [x] row iterator
• [x] Column iterator
• [x] "structured bindings" support for column
• [x] .structured<N>() func
• [x] begin and end
• [x] .size
• [x] .first
• [ ] .last
• [ ] index_of: get the index of a column name
• [ ] operator[]("name")
• [ ] .bind("name", ...)
• [x] Merge sql_cell and stmt_binder
• [ ] Pagination
  • [ ] .pagination()
  • [ ] Pagination iterator
• [ ] Type conversion
  • [ ] Stringify
  • [ ] Dates and times
  • [ ] Convert to possible integer types
  • [ ] Convert float types to possible float values by the driver
  • [ ] Convert JSONValue and JSONDocument to string
    • [ ] Convert json values into string in a way that the strings are always the same (order and stuff)
  • [ ] Convert Readable Collections into json and json into string
  • [ ] Convert images and files into blobs (you need to figure out those types of files)
    • [ ] Using file handle
    • [ ] Predefined image/file/... types that will be implemented in the future

[the-moisrex]

Okay how am I supposed to know the length of the possible columns before-hand?

Should I just let stmt return an object with a column number and a reference to the stmt to invoke?

But what should sql_iterator return then?

• A tuple? of what size?

[the-moisrex]

The problem mentioned above will be fixed using the idea presented in the #136, God willing.