Re: ADD FOREIGN KEY fails, but the records exist
От | Adrian Klaver |
---|---|
Тема | Re: ADD FOREIGN KEY fails, but the records exist |
Дата | |
Msg-id | 22cd11dc-b6de-9056-fbed-1c53065fd1e0@aklaver.com обсуждение исходный текст |
Ответ на | Re: ADD FOREIGN KEY fails, but the records exist (Ron <ronljohnsonjr@gmail.com>) |
Ответы |
Re: ADD FOREIGN KEY fails, but the records exist
Re: ADD FOREIGN KEY fails, but the records exist |
Список | pgsql-general |
On 2/15/21 8:23 AM, Ron wrote: > On 2/15/21 10:17 AM, Adrian Klaver wrote: >> On 2/15/21 8:12 AM, Ron wrote: >>> Postgresql 12.5 >>> >> The error: >> >> DETAIL: Key (amended_response_id, part_date)=(103309154, 2021-01-06 >> 00:00:00) is not present in table "employer_response" >> >> is pointing at 103309154 for amended_response_id = >> employer_response_id. You are showing an employer_response_id of >> 103309156 > > But my query's WHERE clause specifies "amended_response_id = > 103309154;" (I've highlighted it, if you have a GUI MUA.) Yes but amended_response_id is referencing employer_response_id. So do you have a record that matches: employer_response_id part_date 103309154 2021-01-06 00:00:00 > >> >>> >>> >>> sides=> select employer_response_id, part_date >>> from strans.employer_response_p2021_01 >>> where *amended_response_id = 103309154; * >>> employer_response_id | part_date >>> ----------------------+--------------------- >>> 103309156 | 2021-01-06 00:00:00 >>> (1 row) >>> >>> >> >> > > -- > Angular momentum makes the world go 'round. -- Adrian Klaver adrian.klaver@aklaver.com
В списке pgsql-general по дате отправления: