exists.
Your "username" may have changed.
--
Richard Damon
--
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/
ogle.com/d/msgid/sqlalchemy/b5e4faee-5cd6-4b9b-936b-0d80458f55e4n%40googlegroups.com
<https://groups.google.com/d/msgid/sqlalchemy/b5e4faee-5cd6-4b9b-936b-0d80458f55e4n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Richard Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object R
On 5/2/21 6:34 PM, Mike Bayer wrote:
>
>
> On Sun, May 2, 2021, at 4:44 PM, Richard Damon wrote:
>> I asked this a bit ago, but never got an answer, so trying again wording
>> a bit different to see if I can get help.
>
> sorry if this got missed.
>
>>
>>
ld be a simple matter of writing the data into the
Engineer table with an INSERT, forcing the ID to match the ID of the
employee, and then change the value of the type field in the Employee
table with an UPDATE. The question is, is there a more "ORM' way to do this?
--
Richard Damo
structures to actually do some of the work?
I don't think I can just create a new derived object with the original
primary key, as that will get rejected as a duplicate key, not replace
the object.
--
Richard Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object Relation
attr(self, '1st_period') would be the equivalent of self.1st_period,
but not have the name parsed by Python.
--
Richard Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, a
rm/extensions/declarative/api.html?highlight=instrument_declarative#sqlalchemy.ext.declarative.instrument_declarative>
>
>
> which can be turned into an equivalent decorator.
>
> that said I have not yet experimented with mapping classes that are
> also extending ABCMeta so I'm not sure if there are other iss
posed to work, or am I missing some other trick?
Side question, when doing this sort of mix-in, does the order of the
mix-in and declarative_base matter, or is there a real preference?
--
Richard Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchem
Thank you, that looks like what I was looking for but didn't know what
it was called.
On 10/8/20 4:55 AM, Simon King wrote:
> On Thu, Oct 8, 2020 at 3:38 AM Richard Damon wrote:
>> I am working on a app using SQLAlchemy's ORM layer to interface to the
>> database, but I
a
database suitable representation, and I see an option to add a
'reconstructor' to convert a value read from the database into an
object. Is there a similar way that when writing the object, to indicate
how to convert the object into a format that can be put into the database?
--
Richar
and caused a more complicated one)
>
I think you need to post the basics of the code. See the link below
about making it a MCVE
There is obviously something you aren't describing, or we need to see to
point to you what you are missing.
--
Richard Damon
--
SQLAlchemy -
The Python SQ
me. Why
> can't I just have a foreign key to that table? It's a simple many to one
>
>
> @Richard: you can use @declared_attr.cascading to cascade the
> mapper_args to your child classes.
> On Friday, August 28, 2020 at 2:56:02 PM UTC-4 Richard Damon wrote:
>
>
ld be ok.
On 9/3/20 10:25 AM, Mike Bayer wrote:
> yup that was the idea
>
>
> On Thu, Sep 3, 2020, at 10:24 AM, Richard Damon wrote:
>> I have a large number (around a dozen or more, and likely to grow) of
>> derived classes, so I was hoping to cut down repetition with the
&g
ss but this depends on what
> you're doing.
>
>
>
> On Thu, Sep 3, 2020, at 7:24 AM, Richard Damon wrote:
>> I've tried taking my code and changing the ForeignKey to be to Node, and
>> that doesn't change the Warning.
>> Is the problem trying to DRY wi
ame__ = 'Name'
>
> node_id = Column(Integer, ForeignKey("Property.node_id"),
> primary_key=True)
>
> __mapper_args__ = {
> "polymorphic_identity": "Name",
> "inherit_condition": node_id == Property.node_id,
> }
&
try, a little bit dated but the general idea is still
> there, at:
>
> https://docs.sqlalchemy.org/en/13/faq/ormconfiguration.html#i-m-getting-a-warning-or-error-about-implicitly-combining-column-x-under-attribute-y
>
> for joined table inheritance, where Name(Node) -> node_id a
is working just fine, it is just where it hits the
3rd level that it seems to want something explicit.
--
Richard Damon
--
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
gt;
>
> class Foo(...):
> __mapper_args__ = {
> "inherit_condition": node_id == Node.node_id
> }
>
--
Richard Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal,
s of DRY, since all of the
subclasses have the same node_id declaration, and basically the same
__mapper__ is there a way I can add this to Node to push this into the
subclasses? Would I use a @declared_attr, which would need to check if
the type was Node since it is different?
(Background, lo
mn definitions into the
table_args for the table (but that loses the column object)
--
Richard Damon
--
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
27;t use it as a variable name, as that would cause
issues, but in an explicit scope like a class it works.
--
Richard Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCVE: Minimal, Complete, and Verifi
e data.
On 7/7/20 12:46 AM, Mike Bayer wrote:
>
>
> On Mon, Jul 6, 2020, at 11:19 PM, Richard Damon wrote:
>> SQLite allows a program to attach multiple databases to a single
>> connection, and you are able to reference tables in these additional
>> databases with thing
ich would let me do a lot of
the work down in the database engine. I also have found being able to
bind different sets of tables into different engines, but in my case the
database will have the same set of tables, so this doesn't look to work.
--
Richard Damon
--
SQLAlchemy -
The Pyt
if it wasn't an alias shows it following the inserted data,
so I guess it is becoming the named alias for the ROWID.
I think I came across a different section wording that restriction that
wasn't as clear about it, or it was long enough ago that they have
updated that wording to be cleare
for the ROWID. I can't seem to find anything documented to
do to make this happen. I would think this would be a commonly wanted
optimization. Is there something I can do to get this? I would like to
be able to use the ORM.
--
Richard Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object
/ reformatted it to be more or less current:
>
> https://github.com/sqlalchemy/sqlalchemy/wiki/EntityName
>
> note the second example that shows declarative with a mixin, and shows
> how you can use the type() function to generate new classes
> dynamically. Creating new classes in
e base class, or the
decorator could just duck type the needed hooks into the class.
--
Richard Damon
--
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
ke my implementation more DB independent.
>
> Anyhow, thanks again for your note and your work on SQLAlchemy. I
> appreciate it.
>
> Ben
I will admit that wasn't a command I was familiar with, but being DB
Specific it would be something I tend to try to minimize the use of.
ppers might provide such a feature, but that is
NOT part of the base SQL language.
--
Richard Damon
--
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
dress-ids) which would be a violation
of the normal form, and makes operations for creating these
relationships very complicated.
--
Richard Damon THis
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post example code, please provide an MCV
Hey Mike,
Noticed 1.2.5 doesn't have a release date yet
on
http://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-1.2.2.
Was wondering if that could be released sometime soon - we're blocked from
switching over until it's released.
Damon
On Friday, February
Awesome, thanks Mike! Looking forward to the release.
Damon
On Friday, February 23, 2018 at 11:20:33 AM UTC-8, Mike Bayer wrote:
>
> On Fri, Feb 23, 2018 at 1:38 PM, Mike Bayer > wrote:
> > *perfect* test case, I'll get a bug report up and can fix this quickly,
>
mmenting L1 or L3 => no crash
Let me know if there's anything more I can do to clarify/help.
Thanks!
Damon
from sqlalchemy import *
from sqlalchemy.orm import *
from sqlalchemy.ext.declarative import declarative_base
from sqlalchemy import event
Base = declarative_base()
c
gle.com/url?q=https%3A%2F%2Fbitbucket.org%2Fzzzeek%2Fsqlalchemy%2Fissues%2F3944&sa=D&sntz=1&usg=AFQjCNHP34Q9-nl0O_qmczm7uZFo8daCAA>
> .
Thanks!
Damon
On Tuesday, April 4, 2017 at 8:24:07 PM UTC-7, Mike Bayer wrote:
>
> Reusing the original query is hard, and the case you have is du
not what we want here -- we'd just
want "FROM w2"
Replacing
q = orig_query.with_entities(target_cls)
with
q = context.session.query(target_cls).join(orig_query.subquery())
fixes the issue, though this feels less than ideal. Subclassing Query also
seems less than ideal. Do you ha
paring queries. Do you
have a way to compare query equality, or alternatively have a solution to
both of these issues?
Could you also elaborate on what you meant by this comment?
# store this strong reference so recs don't get lost while
# iterating
Thanks again for all your help,
D
Thanks a ton for your help, Mike!
We played around with it and are pretty happy with your solution using the
load() event, so we'll be using that moving forward.
Damon
On Wednesday, March 29, 2017 at 2:40:39 PM UTC-7, Mike Bayer wrote:
>
> I have a working version of b
?
Regarding STI and relationships, is there any way to do that but still get
the benefits of JTI? e.g. is there an easy way to resolve
my_base_class_inst.subclass_prop as a proxy to the subclass? We could roll
our own using __getitem__ but it seems a little hairy.
Thanks again,
Damon
On
lts (or after a list of models
are added to the session?)
- groups the models by type and runs its own subqueries to load the data
Any help here is greatly appreciated!
Thanks,
Damon
--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper
http://www.sqlalchemy.org/
To post exampl
ible to have SA follow similar logic to
construct query objects as well -- in a completely analogous fasion --
when supplied with filters.
Alas that this is not the case. :(
--Damon
On Sep 3, 12:29 pm, "Michael Bayer" wrote:
> Damon wrote:
>
> >> > MUST we explicitly s
t only through an intermediary
table that touches both of them.
--Damon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"sqlalchemy" group.
To post to this group, send email to sqlalchemy@googlegroups.com
lent SA query object by explicitly
supplying the query object the join criteria. But we want SA to *know*
how to infer that join criteria itself. Is this possible?
Thanks in advance,
Damon
--~--~-~--~~~---~--~~
You received this message because you are subscribed to t
42 matches
Mail list logo