如何在Peewee联表查询时避免同名属性被覆盖？

Great question—this is a common gotcha when joining tables with matching field names in Peewee, but luckily there are simple, practical ways around it. Let me walk you through the most reliable solutions:

1. Alias Conflicting Fields Directly #

The quickest fix is to use Peewee's alias() method to give duplicate fields unique names in your result set. This ensures each field gets its own distinct key, so no overwriting occurs.

Example: #

Say you have two tables both with a name field:

from peewee import *

db = SqliteDatabase('app.db')

class User(Model):
    id = PrimaryKeyField()
    name = CharField()  # Duplicate field name

    class Meta:
        database = db

class Post(Model):
    id = PrimaryKeyField()
    author = ForeignKeyField(User, backref='posts')
    name = CharField()  # Same field name as User

    class Meta:
        database = db

When querying, alias the duplicate fields to make them unique:

# Select with aliases to prevent overwrites
query = (User
         .select(
             User.id,
             User.name.alias('author_name'),  # Rename User's name
             Post.name.alias('post_title')     # Rename Post's name
         )
         .join(Post, on=(User.id == Post.author)))

# Access the aliased fields directly from result rows
for row in query:
    print(f"Author: {row.author_name}, Post: {row.post_title}")

2. Select Entire Models and Access via Object Attributes #

If you need most or all fields from both tables, select the full model instances instead of individual fields. This lets you access each table's fields through their respective model objects, eliminating naming conflicts entirely.

Example: #

# Select complete User and Post model instances
query = (User
         .select(User, Post)
         .join(Post))

# Access fields through the model objects
for user in query:
    print(f"User's name: {user.name}")
    print(f"Post's name: {user.post.name}")  # Get Post's name via the related object

This approach keeps your code clean and avoids having to alias every conflicting field—perfect for tables with multiple duplicate column names.

3. Use Tuples or NamedTuples for Result Sets #

If you prefer working with raw data tuples, use tuples() on your query and map results to a named tuple to clearly track which field belongs to which table.

Example: #

from collections import namedtuple

# Define a named tuple to map result columns
UserPostResult = namedtuple('UserPostResult', ['user_id', 'user_name', 'post_name'])

# Query returns tuples instead of model instances
query = (User
         .select(User.id, User.name, Post.name)
         .join(Post)
         .tuples())

# Map each tuple to the named tuple for explicit access
for row in query:
    result = UserPostResult(*row)
    print(f"User ID: {result.user_id}, User Name: {result.user_name}, Post Name: {result.post_name}")

Why This Happens #

Peewee uses field names as keys when building result rows (either as model attributes or dictionary keys). When two fields share the same name, the later one in your select statement overwrites the earlier one. All the solutions above work by ensuring each field has a unique identifier in the final result set.

内容的提问来源于stack exchange，提问作者user2950747