buildbot/buildbot — comment on commit 8b1cee84683fd185d46aea193a01f2b42b4f5503
File: master/buildbot/db/migrate/versions/011_add_buildrequest_claims.py line 67
By benallard:

We only tried, since now, with SQLite. Even if they don't use the foreign key constraint (by default, you can enable this with a pragma call), you can still ask them to the table definition. I'll try to get to the actual one later, but we noticed that for this special table, they weren't present with the last table version.

On 26 nov. 2011, at 18:21, "Dustin J. Mitchell" wrote:

> I can't reproduce this - sqlite and mysql/myisam don't use foreign keys, so I'm assuming you mean with postgres. And with the most recent database version, I see
>

> metabuildslave=# SELECT
> tc.constraint_name, tc.table_name, kcu.column_name,
> ccu.table_name AS foreign_table_name,
> ccu.column_name AS foreign_column_name
> FROM
> information_schema.table_constraints AS tc
> JOIN information_schema.key_column_usage AS kcu ON tc.constraint_name = kcu.constraint_name
> JOIN information_schema.constraint_column_usage AS ccu ON ccu.constraint_name = tc.constraint_name
> WHERE constraint_type = 'FOREIGN KEY';
> constraint_name | table_name | column_name | foreign_table_name | foreign_column_name
> -----------------------------------------------+------------------------------+---------------+--------------------+---------------------
> change_properties_changeid_fkey | change_properties | changeid | changes | changeid
> change_files_changeid_fkey | change_files | changeid | changes | changeid
> sourcestamp_changes_changeid_fkey | sourcestamp_changes | changeid | changes | changeid
> sourcestamp_changes_sourcestampid_fkey | sourcestamp_changes | sourcestampid | sourcestamps | id
> scheduler_changes_changeid_fkey | scheduler_changes | changeid | changes | changeid
> scheduler_changes_schedulerid_fkey | scheduler_changes | schedulerid | schedulers | schedulerid
> change_links_changeid_fkey | change_links | changeid | changes | changeid
> sourcestamps_patchid_fkey | sourcestamps | patchid | patches | id
> buildsets_sourcestampid_fkey | buildsets | sourcestampid | sourcestamps | id
> scheduler_upstream_buildsets_schedulerid_fkey | scheduler_upstream_buildsets | schedulerid | schedulers | schedulerid
> scheduler_upstream_buildsets_buildsetid_fkey | scheduler_upstream_buildsets | buildsetid | buildsets | id
> buildset_properties_buildsetid_fkey | buildset_properties | buildsetid | buildsets | id
> builds_brid_fkey | builds | brid | buildrequests | id
> buildrequests_buildsetid_fkey | buildrequests | buildsetid | buildsets | id
> users_info_uid_fkey | users_info | uid | users | uid
> object_state_objectid_fkey | object_state | objectid | objects | id
> buildrequest_claims_objectid_fkey | buildrequest_claims | objectid | objects | id
> buildrequest_claims_brid_fkey | buildrequest_claims | brid | buildrequests | id
> change_users_uid_fkey | change_users | uid | users | uid
> change_users_changeid_fkey | change_users | changeid | changes | changeid
> (20 rows)
>

>
> in particular, `buildrequests_buildsetid_fkey` is still there.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/buildbot/buildbot/commit/8b1cee84683fd185d46aea193a01f2b42b4f5503#commitcomment-747834