<commit_before>Running updates
===

Yes, I will make this more seamless in the future.

For now, you only need to run "new" updates (although the sql should
prevent multiple modifications).

e.g.

  $ psql --user=$USER --password --host=$HOST $DB <
update\_20140707.sql

will run the update for 20140707.sql.

The output will indicate '1' for a successful execution or '0' if the
command was not run (error, or unneeded)

$USER is a placeholder for the "db.user" value defined in config.ini,
$HOST is a placeholder for the "db.host" value defined in config.ini,
$DB   is a placeholder for the "db.db"   value defined in config.ini,
When prompted for a password, use the value of "db.password" defined
in config.ini
<commit_msg>because I like bonus points<commit_after>Running updates
===

Yes, I will make this more seamless in the future.

For now, you only need to run "new" updates (although the sql should
prevent multiple modifications).

e.g.

```  $ psql --user=$USER --password --host=$HOST $DB <
update\_20140707.sql
```

will run the update for 20140707.sql.

The output will indicate '1' for a successful execution or '0' if the
command was not run (error, or unneeded)

$USER is a placeholder for the "db.user" value defined in config.ini,
$HOST is a placeholder for the "db.host" value defined in config.ini,
$DB   is a placeholder for the "db.db"   value defined in config.ini,
When prompted for a password, use the value of "db.password" defined
in config.ini

{'fraction_non_alphanumeric': 0.08949152542372882, 'fraction_numerical': 0.02440677966101695, 'mean_word_length': 3.9864864864864864, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3570224', 'n_tokens_mistral': 464, 'n_tokens_neox': 432, 'n_words': 218}