Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Switch from Redis to Postgres? #4

Closed
dvfeinblum opened this issue Sep 26, 2018 · 2 comments
Closed

Switch from Redis to Postgres? #4

dvfeinblum opened this issue Sep 26, 2018 · 2 comments
Assignees
@dvfeinblum
Labels
enhancement New feature or request question Further information is requested

Comments

@dvfeinblum
Copy link
Owner

Still waffling back and forth a bit on this. It'd be nice to use postgres instead because at some point, I may want to be able to do more than just count stuff. Plus too, redis isn't exactly amenable to doing the sort of counting I may want to do.
@dvfeinblum dvfeinblum added the question Further information is requested label Sep 26, 2018
@dvfeinblum dvfeinblum changed the title Switch from Redis to Postgres Switch from Redis to Postgres? Sep 26, 2018
@dvfeinblum
Copy link
Owner Author

Yeah; I think I'm definitely gonna do this. The most obvious schema that comes to mind is to just do

word count pos
dog 13 NN

and then we could even do

url word count
foobar.blog/2018-09-01-entry-about-cats cat 3092

Obviously, if we wanted the code to be simpler, we could skip the count column and just do SELECT COUNT(*) WHERE URL='' AND word=''; but I like a little preaggregation.

This'll be nice because we can centralize the information (nltk/word count) in one db instead of having two.

@dvfeinblum dvfeinblum self-assigned this Oct 21, 2018
@dvfeinblum dvfeinblum added the enhancement New feature or request label Oct 21, 2018
dvfeinblum added a commit that referenced this issue Oct 27, 2018
@dvfeinblum
[Issue #4] Create Postgres DB (#9)
91656a0 
* Added sqitch boilerplate and create word_details table

* created blog_details table

* Dockerized db and updated README
@dvfeinblum dvfeinblum mentioned this issue Oct 27, 2018
Merged
dvfeinblum added a commit that referenced this issue Oct 27, 2018
@dvfeinblum
[Issue #4] Use New Lexicount DB (#11)
38a4946 
* Added a blog_parser role and fleshed out basic db_utils

* Added a mock client for testing and built out some queries

* Finished all queries and they actually work.

* Updated unittests

* Added myself as a user for tomfoolery
@dvfeinblum
Copy link
Owner Author

Yes we can.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dvfeinblum dvfeinblum

Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dvfeinblum