Project

General

Profile

« Previous | Next » 

Revision 4985

README.TXT: Documented that if the row-based and column-based imports produce different inserted row counts, this usually means that a table is underconstrained (the unique indexes don't cover all possible rows). The inserted row count difference occurs because column-based import collapses empty table rows into one insert, while row-based import performs an insert of the empty row for each input row. Without a unique index to combine multiple row-based inserts, extra rows will be added.

View differences:

README.TXT
198 198
Testing:
199 199
    Mapping process: make test
200 200
        Including column-based import: make test by_col=1
201
            If the row-based and column-based imports produce different inserted
202
            row counts, this usually means that a table is underconstrained
203
            (the unique indexes don't cover all possible rows).
204
            This can occur if you didn't use COALESCE(field, null_value) around
205
            a nullable field in a unique index. See sql_gen.null_sentinels for
206
            the appropriate null value to use.
201 207
    Map spreadsheet generation: make remake
202 208
    Missing mappings: make missing_mappings
203 209
    Everything (for most complete coverage): make test-all

Also available in: Unified diff