Re: [sqlalchemy] complex primary key with server_default timestamp

On 05/15/2017 06:43 AM, mdob wrote: Just curious. Let's say we have a complex primary key of user_id (integer), project_id (integer) and date (timestamp). After adding and committing we don't have the PK and we won't be able to update it. Is that right? if you were using Postgresql this wou

[sqlalchemy] complex primary key with server_default timestamp

Just curious. Let's say we have a complex primary key of user_id (integer), project_id (integer) and date (timestamp). After adding and committing we don't have the PK and we won't be able to update it. Is that right? If it was auto-increment integer then it would probably be fine. PK would be