Kiran Jonnalagadda
Kiran Jonnalagadda
Notes: https://github.com/jeffwidman/sqlalchemy-postgresql-materialized-views
Migrations, and always make a copy of the model in the migration.
This won't work because we don't use Alembic for new deployments. See point 6 in hasgeek/coaster#100.
Have you tried using `__abstract__` to prevent table creation? http://docs.sqlalchemy.org/en/latest/orm/inheritance.html?highlight=abstract#abstract-concrete-classes
#465 introduces tweet ids stored inside the JobPost model.
@iambibhas Here is how this is supposed to work. First, we recognise three states for a user's identity: 1. **Unknown**: We know nothing about this client. It's new, and it...
I missed this while away at Hillhacks. I'd love to take this on as an official feature in Hasjob, and I think a few technical optimisations will help. Rather than...
Just pinging to say I haven't forgotten this yet. We're currently working on [HGTV](/hasgeek/hasgeek.tv) and will follow that with [Funnel](/hasgeek/funnel), and after that do a massive revamp of Hasjob. I'll...
Engine Yard has a nice blog post on [PostgreSQL partitioning, including a trigger that creates child tables automatically](https://blog.engineyard.com/2013/scaling-postgresql-performance-table-partitioning).
One expectation with partitioning is that old data that is no longer needed can be exported to a backup and removed from the database. In our case we still read...