On 7/26/15 4:39 PM, Jinghui Niu wrote:
Thanks Mike,
I've read the documentation on both, hybrid attributes seem to be
easier and have a clearer logic in this use case. Although this is
just my gut feeling as a layman. What is the rationale behind having
two competing solutions?
Also, I dimly remember someone recommended using "property method", I
didn't quite understand it back then, does it relate to the two
techniques you suggested here?
composites are a much older feature and very specific to the
multiple-columns use case, but should work here. hybrids are more open
ended, more flexible and probably easier to understand. sounds like a
"property method" to me, e.g. a Python descriptor.
On Sun, Jul 26, 2015 at 11:06 AM, Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>> wrote:
On 7/25/15 6:38 PM, Jinghui Niu wrote:
By the way, the database driver that I'm using is SQLite, which
doesn't support native timestamp I believe.
On Saturday, July 25, 2015 at 2:21:44 PM UTC-7, Jinghui Niu wrote:
I'm using two columns to store my datetime records: one
column stores utc timestamp as a string, the other column
stores a timezone offset as an integer. Now I find myself
most of the time writing ad hoc functions to convert those
UTC times to various local times. My code base has become
really inconsistent and repetitive.
I'm looking to write some code with sqlalchemy, natively
sqlalchemy, to allow me to get the converted local time on
each query, automatically. I've heard of that feature before.
I'm kind of lost in the documentation. Could someone point a
general direction here? I don't expect too much, just a
general direction would be highly appreciated. Thanks a lot.
--
there are multiple documented techniques for this kind of thing.
Have you looked into composite attributes or hybrid properties ?
Both can suit this use case.
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
<mailto:sqlalchemy+unsubscr...@googlegroups.com>.
To post to this group, send email to sqlalchemy@googlegroups.com
<mailto:sqlalchemy@googlegroups.com>.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in
the Google Groups "sqlalchemy" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/sqlalchemy/qWh8o5bGzU4/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to sqlalchemy+unsubscr...@googlegroups.com
<mailto:sqlalchemy+unsubscr...@googlegroups.com>.
To post to this group, send email to sqlalchemy@googlegroups.com
<mailto:sqlalchemy@googlegroups.com>.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
--
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
<mailto:sqlalchemy+unsubscr...@googlegroups.com>.
To post to this group, send email to sqlalchemy@googlegroups.com
<mailto:sqlalchemy@googlegroups.com>.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
--
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 post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at http://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.
