libtabula

Check-in [22689bd7dc]
Login

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

Overview
Comment:.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:22689bd7dc1389e105d4ecd8f0c83fbfa68c0ea0
User & Date: etr 2015-09-03 14:37:09
Context
2015-09-11
18:30
Added a test for C++11's "long long" data type, which we use in defining sql_* data types. Previously, we blindly assumed the C++ compiler also supported C99's "long long" even though C++98 and C++03 don't require it, which in turn required a couple of levels of fall-back for the cases where the C++ compiler didn't have that extension. Now that it's finally part of C++, we can just check for it. check-in: dd77d4c60e user: etr tags: trunk
2015-09-03
14:37
. check-in: 22689bd7dc user: etr tags: trunk
2015-08-15
10:11
Fixed some errors introduced in the recent merge check-in: 7e59757bd5 user: tangent tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to Wishlist.md.

202
203
204
205
206
207
208






209
210
211
212
213
214
215

    -   Map C API error numbers to libtabula constants in
        DBDriver::errnum().  Rename to error_code()?

    -   Must create at least two other DBDriver subclasses to
        ensure base class is reusable before releasing v4.0.
        PostgresDriver and SQLiteDriver?







    -   Templatize all classes that use DBDriver interface with the
        DB driver type.  This lets you specify the driver type to use
        with a Connection and all its children without modifying the
        existing method parameter lists.  This also lets us worry less
        about C API types, as they can be hidden away behind typedefs:








>
>
>
>
>
>







202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221

    -   Map C API error numbers to libtabula constants in
        DBDriver::errnum().  Rename to error_code()?

    -   Must create at least two other DBDriver subclasses to
        ensure base class is reusable before releasing v4.0.
        PostgresDriver and SQLiteDriver?

    -   Maybe create DummyDriver, which would let us put more of the
        library under the test suite.  Our excuse for not doing
        that before is that many operations required a DB server
        conn and cooperating classes, but if we can mock the DBMS,
        we can treat the other classes as separately-testable units.

    -   Templatize all classes that use DBDriver interface with the
        DB driver type.  This lets you specify the driver type to use
        with a Connection and all its children without modifying the
        existing method parameter lists.  This also lets us worry less
        about C API types, as they can be hidden away behind typedefs: