Hi,
The problem I'm trying to solve is I've created a multi-temporal relational
table construct (à la bitemporality) that I want to create SQLAlchemy Core
composite operations for (and eventually SQLAlchemy ORM).
Let's call these TemporalRelationSet's. I've subclassed SchemaItem. I also
do
On 11/30/2015 12:54 PM, Alyssa Kwan wrote:
> Hi,
>
> The problem I'm trying to solve is I've created a multi-temporal
> relational table construct (à la bitemporality) that I want to create
> SQLAlchemy Core composite operations for (and eventually SQLAlchemy ORM).
>
> Let's call these
On 11/30/2015 02:29 PM, Alyssa Kwan wrote:
> Thanks Michael,
>
> These constructs are actually composed of 3 tables - the temporal data
> itself, a clock table, and an element clock table - both the clocks keep
> track of points in time that exist within time ranges since ranges are
> lossy.
Thanks, Michael!
Any thoughts on the autoload?
Thanks,
Alyssa
On Monday, November 30, 2015 at 11:43:30 AM UTC-8, Michael Bayer wrote:
>
>
>
> On 11/30/2015 02:29 PM, Alyssa Kwan wrote:
> > Thanks Michael,
> >
> > These constructs are actually composed of 3 tables - the temporal data
> >
Thanks Michael,
These constructs are actually composed of 3 tables - the temporal data
itself, a clock table, and an element clock table - both the clocks keep
track of points in time that exist within time ranges since ranges are
lossy. Does this advice still hold? A related requirement is
On 11/30/2015 02:51 PM, Alyssa Kwan wrote:
> Thanks, Michael!
>
> Any thoughts on the autoload?
I'd assume you'd want to use a naming convention.
e.g. my_autoload('mything') looks for tables 'mything_temporal',
'mything_clock', 'mything_element_clock', something like that.
>
> Thanks,
>
