【发布时间】:2019-10-21 08:39:08
【问题描述】:
经过一番折腾,我已经接近了(为了我,我不在乎类型差异)。但是,我确实想要与 MySQL 完全相同的输出格式。原因是我正在尝试调整仅 MySQL 的工具以与 PostgreSQL 一起使用。这是 MySQL 的示例输出(尽管列较少):
mysql> show columns from users;
+-------------+--------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+--------------+------+-----+---------+-------+
| id | int(11) | NO | PRI | NULL | |
| name | varchar(200) | YES | | NULL | |
| institution | varchar(200) | YES | | NULL | |
+-------------+--------------+------+-----+---------+-------+
这是我正在测试的表:
Table "public.users"
Column | Type | Collation | Nullable | Default
--------------------+------------------------+-----------+----------+-----------------------------------
id | integer | | not null | nextval('users_id_seq'::regclass)
name | character varying(255) | | |
role_id | integer | | |
image_url | character varying(510) | | |
institution | character varying(255) | | |
qualifications | text | | |
cv_url | character varying(510) | | |
specializations | text | | |
text_collaboration | text | | |
Indexes:
"users_pkey" PRIMARY KEY, btree (id) Check constraints:
"users_name_not_null" CHECK (name IS NOT NULL) Foreign-key constraints:
"fk_role_id" FOREIGN KEY (role_id) REFERENCES roles(id) Referenced by:
TABLE "novel_reviews" CONSTRAINT "novels_reviewer_id_fkey" FOREIGN KEY (reviewer_id) REFERENCES users(id)
TABLE "review_translations" CONSTRAINT "review_translations_recorder_id_fkey" FOREIGN KEY (recorder_id) REFERENCES users(id)
这是我的查询......它可能做得不好,尤其是。使用 GROUP BY 部分:
SELECT column_name AS "Field"
, data_type AS "Type"
, is_nullable AS "Null"
, CASE WHEN is_primary=true THEN 'PRI' ELSE NULL END AS "Key"
, column_default as "Default"
, CASE WHEN column_default LIKE 'nextval(%' THEN 'auto_increment' ELSE '' END AS "Extra"
FROM
(
SELECT c.column_name
, c.data_type
, c.is_nullable
, tc.constraint_type='PRIMARY KEY' AS is_primary
, c.column_default
FROM information_schema.columns AS c
LEFT JOIN information_schema.constraint_column_usage AS ccu USING (column_name, table_name)
LEFT JOIN information_schema.table_constraints tc USING (constraint_name)
WHERE c.table_name = 'users'
GROUP BY c.column_name
, c.data_type
, c.is_nullable
, is_primary
, c.column_default
) as sq;
这是我目前得到的结果。很抱歉格式不好。
> Field | Type | Null | Key | Default | Extra
> --------------------+-------------------+------+-----+-----------------------------------+----------------
> | cv_url | character varying | YES | |
> | id | integer | NO | | nextval('users_id_seq'::regclass) | auto_increment
> | id | integer | NO | PRI | nextval('users_id_seq'::regclass) | auto_increment
> | image_url | character varying | YES | |
> | institution | character varying | YES | |
> | name | character varying | YES | |
> | qualifications | text | YES | |
> | role_id | integer | YES | |
> | specializations | text | YES | |
> |
> | (10 rows)
我不知道如何让第二次出现的 id 消失,即来自非主键约束的那个。我不知道如何放弃它。我尝试做WHERE is_primary_key is NULL or is_primary_key=TRUE,但这也删除了Name 字段,该字段加入了一个也不是主键的约束。
如果字段是主键,我想要从表中获取所有列(每列仅一次)和字符串“PRI”。
帮助!我有点过头了。谢谢。
【问题讨论】:
-
首先使用
-E开关运行psql,这将回显各种反斜杠命令后面的所有SQL。然后可以\d users查看psql用来描述users表的SQL。 -
这很有趣。我设法找到正在运行的查询来生成它。但是,postgres 在其
\d命令中没有指示“键”或主键约束或类似内容的列,因此它不是直接帮助。编辑:我猜它确实有索引。不过,我需要弄清楚如何组合这些信息。
标签: sql postgresql information-schema