On Fri, Jul 18, 2014 at 10:58 AM, Stephen Broberg <[email protected]> wrote:
> > As for the .fullschema thing, a few questions: > > 1. Does just produce the DDL, or does it generate data as well? Just > the DDL in this case would not be particularly useful, as you'd need the db > populated to accurately reproduce the scenario. If it's only DDL, then I > could just give you the files we use to create our schema. > The ".fullschema" command dumps the schema and the sqlite_statN tables (for N of 1, 3, and 4). If you have SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 turned on, then the sqlite_stat3 or sqlite_stat4 tables will likely contain samples of real data. Most of the real data is omitted, but there is some content in the samples. The sqlite_stat1 table contains statistics about real data (such as the number of rows in each table and the average number of repeated values in each column) but no actual data. > 2. If it produces DML as well, does it obfuscate data? I'm guessing > not – that seems a rather sophisticated feature. I wouldn't want to > include confidential data in a bug report. > The .fullschema command does not obfuscate the samples. If you are using STAT3 or STAT4 and need to submit a report, either run "DELETE FROM sqlite_stat3; DELETE FROM sqlite_stat4;" before submitting, or create a separate "test" database that demonstrates your problem but has been sanitized of sensitive data. Paid support customers are automatically covered under an NDA and can send the SQLite development team STAT3 and STAT4 data via private email, if they desire. > 3. Whether it produces the DDL or DDL+data, either one would be too > large to include in these messages, which have a limit I exceeded the first > time I tried to submit the issue. How do I attach large files to these > messages? Just link to something like paste bin or Google Docs? > If your DDL won't fit in an [email protected] post, please try to cut it down to only include tables that are in your query. If that doesn't work, putting the info ona paste bin or google docs and sending a link is a good backup plan. Paid support customers can send direct email, of course, and are not subject to the message size limitations. FWIW, We limit the size of messages on [email protected] for the sake of the 1000s of subscribers on that list, and to spare them having to load unnecessary content. The size limits are *not* a ploy to try to get more paid support customers. Truly. If you really, really need to post an over-size message to [email protected], we can give you a temporary size-limit exemption by prior arrangement. -- D. Richard Hipp [email protected] _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
