You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "vincbeck (via GitHub)" <gi...@apache.org> on 2023/02/27 20:55:41 UTC

[GitHub] [airflow] vincbeck commented on pull request #29776: Add Pydantic-powered ORM models serialization for internal API.

vincbeck commented on PR #29776:
URL: https://github.com/apache/airflow/pull/29776#issuecomment-1447074961

   > We only need one-way converstion (from database models to Python models), because all the DB operations and modifications of the Database entries will be done in the internal API server, so the server side of any method will be able to use primary key stored in the serializable object, to retrieve the actual DB model to update.
   
   Quick question. If we take this approach, why do we need then to send the whole serialized object and not the primary keys only? Is it to avoid to have to refactore too many functions and have a backward compatible solution? I am not saying it is saying, I am just curious :)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org