<div dir="ltr">Hi Tobiah! Soon we will release a migration tool which should help with updating the database schema. Until this, during the early stage of development you can drop all tables and re-create them: # update_db.py from models import db from settings import db_params from initial_data import populate_database db.bind(**db_params) db.generate_mapping(check_tables=False) db.drop_all_tables(with_all_data=True) db.create_tables() populate_database() Best regards, Alexander Kozlovsky </div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Oct 3, 2017 at 12:05 AM, Tobiah <<a href="mailto:toby@tobiah.org" target="_blank">toby@tobiah.org</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm new to ORMs in general. I used the online tool to create a set of entities and used the resulting python class set in a python program to automatically generate a mysql database. Now I've decided that I want to change one of my 'int' types to a 'str'. I did this in the corresponding class and re-ran the program, but my database field type was not updated. How does one normally handle a changing schema during development? Do you have to puff the database and rebuild every time there is a change? Also, does anyone ever somehow generate the Pony classes at runtime based on introspection of the database? Thanks, Tobiah _______________________________________________ ponyorm-list mailing list <a href="mailto:ponyorm-list@ponyorm.org" target="_blank">ponyorm-list@ponyorm.org</a> <a href="/ponyorm-list" rel="noreferrer" target="_blank">https://mailman-mail5.webfaction.com/listinfo/ponyorm-list</a> </blockquote></div> </div>