tomasguisasola
commented
7 years ago Hi speeder
Yes, that is the expected behavior: the database NULL value is always converted to Lua as a nil. Note the last sentence in the docs:
http://keplerproject.github.io/luasql/manual.html#cur_fetch
If you want to know the names of the columns, you should use the appropriate cursor method:
http://keplerproject.github.io/luasql/manual.html#cur_colnames
Also note that some drivers offers additional methods that could be useful.
Regards, Tomás
On 2016-12-15 21:52, speeder wrote:
The program here uses "a" setting on fetching to get column names to put stuff inside (example: as it loops through rows, it can go adding things to each column, or it can use column names to dynamically print a page that dumps all columns).
But if the contents of the field on the first row is null, it doesn't return the columns either, breaking stuff. (for example by creating a webpage that has columns than needed when dumping data if by bad luck several of the first fetched data had NULLs in those columns in first place).
-- You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub [1], or mute the thread [2].
*
Links:
[1] https://github.com/keplerproject/luasql/issues/66 [2] https://github.com/notifications/unsubscribe-auth/AAIA7ZUxtzefc4OKW6TXRWD5xOh2hrF1ks5rIdK0gaJpZM4LOtEM
speeder
The program here uses "a" setting on fetching to get column names to put stuff inside (example: as it loops through rows, it can go adding things to each column, or it can use column names to dynamically print a page that dumps all columns).
But if the contents of the field on the first row is null, it doesn't return the columns either, breaking stuff. (for example by creating a webpage that has columns than needed when dumping data if by bad luck several of the first fetched data had NULLs in those columns in first place).