M. Bahoosh
M. Bahoosh
### Row - rows, columns, and cells - a data view or owner or retriever but nothing more ### Statement - represents the whole query - we can use the...
 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...
The problem mentioned above will be fixed using the idea presented in the #136, God willing.
## other names - `resizable_tuple` - `istl::tuple` - `mituple` - `mi_tuple` - `expandable_tuple` - `ituple` for improved tuple
I've already implement most of it here: https://github.com/the-moisrex/codeshells/blob/main/cpp.tuple.structured.binding/main.cpp
It's done now. I just have to figure out how to decompose this in a for loop.
Do I have to reimplement all of the ituple_iterator just like I did with rapidjson? Come on!
Somewhere along the way I forgot how sql statement was made and now I can't use ituple for it without changing what ituple is now.
## Lazy Iterators Seems like a good idea to be used here.
It was more than a year ago, I don't remember the clang bug. But based on the version specified in [this close proximity commit](https://github.com/the-moisrex/webpp/commit/ac198d9b085f4abdb8be2747f0a1143abaae7108), I think it was clang version...