Parser needs to be able to update existing database, not just create a new one

[elze]

The parser needs to be able to take new job ads from the directory specified in the IMPORT_FILE_PATH in import_settings.cfg, parse them, and update corresponding rows in the database. When it encounters a skill_term that's already in the skill_post_counters table, it needs to update number_of_postings for that skill_term. And for each secondary term it needs to update the number_of_times field in the corresponding row in the skill_pairs table.

[bluflowr]

Two options on finding a match in the db. An initial load of the skill_terms in the skill_post_counters table into a dict or a db call for each lookup. I'm inclined to go with the former.

[elze]

Hi Irma,

Sure, you can load all the skill_terms in one database call. Implement it
however you see fit, and we can review it later, maybe at the PyMoms
meeting if you have the time to do it by then.

Elze

On Thu, Nov 12, 2015 at 11:22 AM, Irma Kramer notifications@github.com
wrote:

Two options on finding a match in the db. An initial load of the
skill_terms in the skill_post_counters table into a dict or a db call for
each lookup. I'm inclined to go with the former.

—
Reply to this email directly or view it on GitHub
#3 (comment).