libtabula

Check-in [97073e9aa4]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Removed "Initializing result set objects" from the "tricky bits" section of the Wishlist section on DB independence, since it now basically boils down to the Row and Field items just added, and those are more specific.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 97073e9aa4e181aaa38dfbb30da733d4d1ab36d9
User & Date: etr 2015-08-12 21:53:21
Context
2015-08-14
03:54
examples/cgi_jpeg now modifies its output to use LF only in output when running under dtest so the bmark.txt output file doesn't have mixed line endings. There's no reason we have to speak legal HTTP in this case. check-in: 4234731834 user: tangent tags: trunk
2015-08-12
21:55
Merged trunk Wishlist changes again, and removed the type_info item from the DB independence section in anticipation of merging this branch into the trunk, since that's what this branch is addressing. check-in: e039e01875 user: etr tags: mysql-type-info
21:53
Removed "Initializing result set objects" from the "tricky bits" section of the Wishlist section on DB independence, since it now basically boils down to the Row and Field items just added, and those are more specific. check-in: 97073e9aa4 user: etr tags: trunk
21:45
Noted that Field and Row are still intimately tied into the MySQL C API. check-in: dc744e7800 user: etr tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to Wishlist.md.

232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
            template <class DBD = MysqlDriver>
            class UseQueryResult { ...
                DBD::row_type fetch_raw_row();
            }

    -   Tricky bits:

        -   Initializing result set objects.

        -   type_info module.  Extremely closely tied to MySQL C API
            right now.  Will probably have to turn it into a parallel
            class hierarchy to DBDriver, or fold it in with same.

        -   Will CMake let us figure out which DB engines are available
            on non-autoconf systems, or at least pass in options that
            let the user select them?







<
<







232
233
234
235
236
237
238


239
240
241
242
243
244
245
            template <class DBD = MysqlDriver>
            class UseQueryResult { ...
                DBD::row_type fetch_raw_row();
            }

    -   Tricky bits:



        -   type_info module.  Extremely closely tied to MySQL C API
            right now.  Will probably have to turn it into a parallel
            class hierarchy to DBDriver, or fold it in with same.

        -   Will CMake let us figure out which DB engines are available
            on non-autoconf systems, or at least pass in options that
            let the user select them?