View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001461 | SymmetricDS | Improvement | public | 2013-10-31 19:06 | 2025-04-30 17:20 |
| Reporter | rotten | Assigned To | |||
| Priority | normal | ||||
| Status | confirmed | Resolution | open | ||
| Product Version | 3.5.9 | ||||
| Summary | 0001461: dbexport --sql column filter | ||||
| Description | If I run dbexport --sql with a selection query that does not select all of the columns in the table, dbexport will generate a CSV with all of the columns in the original table, and simply not populate the columns I didn't select. I'd rather the CSV only contained the columns I selected. Is that something that can be added as a flag or property? Or maybe simply made the default behaviour when --sql is used? I'm exporting tables to third parties who do not need all of the columns. Rather than shipping them empty columns, I'd like to ship them what they need without having to post-process the CSV. | ||||
| Steps To Reproduce | create table (a, b, c, d) insert some values in all 4 columns. dbexport --sql 'select a,b from table' Note that the csv has a,b,c,d with only a,b with values. | ||||
| Tags | dbimport/dbexport | ||||
|
|
It appears dbexport will work as expected for the scenario above if you add the fields you do not require to the "--exclude-columns" list of fields i.e dbexport --sql 'select a,b from table' --exclude-columns 'c,d' should produce a csv file with just |
|
|
It seems like it's using the table metadata, and it should be using the result set metadata. |