t 2:26 AM, Jacob Pavlock wrote:
>
>
> Mike,
>
> Thanks for the great explanation and the quick response! I think am I
> starting to get it now. I guess the same or similar idea though leads to
> the following (somewhat confusing) behavior:
>
> (I added a repr and setters f
ad no idea you intended this to be the same primary key
> identity because those attributes are not set up front.
>
> When you explicitly set up the three pk attributes on Track, then the
> merge() process can see the apparent primary key you had in mind and it can
> correctly matc
Hello! I am new to sqlalchemy and was hoping to get some insight on the
following issue:
import sqlalchemyfrom sqlalchemy import Column, Integer, Stringfrom
sqlalchemy.ext.declarative import declarative_basefrom sqlalchemy.ext.hybrid
import hybrid_propertyfrom sqlalchemy.orm import
Mike,
Thanks a lot for the response and also for considering this as a future
feature. I've switched to using `attr.ilike(value)` in the meantime and it
is working great.
On Thursday, August 27, 2020 at 2:42:43 PM UTC-5 Mike Bayer wrote:
>
>
> On Thu, Aug 27, 2020, at 2:27 PM, Jaco
I have two classes, a Track and an Album. In order to have album fields
easily accessible from a track, I created an association proxy attribute.
```python
class Track(MusicItem, Base):
__tablename__ = "tracks"
_id = Column(Integer, primary_key=True)
_album_id = Column(Integer,
