FWIW, I recently had a similar situation and ended using 2 tables -- one as
a transaction log and the other with a constantly updated entry. While
your approach worked fine, the database performed significantly better with
2 tables because the (vast) majority of queries only needed the most
Thanks for the book reference Jonathan, it looks very useful!
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, and Verifiable
Example. See http://stackoverflow.com/help/mcve for a
Than you Mike and Jonathan for your replies. I will experiment with this
and let you know how it works out.
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, and Verifiable
On Friday, November 18, 2016 at 2:08:05 PM UTC-5, Paul Giralt wrote:
>
> I'm having trouble figuring out how to accomplish this task using
> SQLAlchemy. Basically I have a table that maps a user's skill levels as
> follows:
>
> class Skillmap(db.Model):
> __tablename__ = 'skillmap'
>
