Thank you, Mike, for the suggestion! Another thought I mulled over was to create a new *point* table and then use a nullable FK from the *vertex* table. That way, the *Point* class can map to its own dedicated table, and a *Vertex* class would then use a relationship that’s able to map optional *Point*s to a *Vertex* via that FK relationship 🤔
Once we get to implementing this, I’ll let you know what we did… -- 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 full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/f3737188-68c0-4eba-9467-a7aaa520df2fn%40googlegroups.com.
