网址的PostgreSQL唯一非顺序ID

时间:2019-05-10 16:56:28

标签: postgresql postgresql-11

我已经看过一些在Stackoverflow上创建字母数字ID的方法,但是它们都有缺点,一些方法没有检查冲突,而其他方法则使用了序列,这在使用逻辑复制时不是一个好选择。

经过一次谷歌搜索,我发现this网站上有以下脚本,该脚本检查冲突并且不使用序列。但是,当将行插入表中时,这是作为触发器完成的。

-- Create a trigger function that takes no arguments.
-- Trigger functions automatically have OLD, NEW records
-- and TG_TABLE_NAME as well as others.
CREATE OR REPLACE FUNCTION unique_short_id()
RETURNS TRIGGER AS $$

 -- Declare the variables we'll be using.
DECLARE
  key TEXT;
  qry TEXT;
  found TEXT;
BEGIN

  -- generate the first part of a query as a string with safely
  -- escaped table name, using || to concat the parts
  qry := 'SELECT id FROM ' || quote_ident(TG_TABLE_NAME) || ' WHERE id=';

  -- This loop will probably only run once per call until we've generated
  -- millions of ids.
  LOOP

    -- Generate our string bytes and re-encode as a base64 string.
    key := encode(gen_random_bytes(6), 'base64');

    -- Base64 encoding contains 2 URL unsafe characters by default.
    -- The URL-safe version has these replacements.
    key := replace(key, '/', '_'); -- url safe replacement
    key := replace(key, '+', '-'); -- url safe replacement

    -- Concat the generated key (safely quoted) with the generated query
    -- and run it.
    -- SELECT id FROM "test" WHERE id='blahblah' INTO found
    -- Now "found" will be the duplicated id or NULL.
    EXECUTE qry || quote_literal(key) INTO found;

    -- Check to see if found is NULL.
    -- If we checked to see if found = NULL it would always be FALSE
    -- because (NULL = NULL) is always FALSE.
    IF found IS NULL THEN

      -- If we didn't find a collision then leave the LOOP.
      EXIT;
    END IF;

    -- We haven't EXITed yet, so return to the top of the LOOP
    -- and try again.
  END LOOP;

  -- NEW and OLD are available in TRIGGER PROCEDURES.
  -- NEW is the mutated row that will actually be INSERTed.
  -- We're replacing id, regardless of what it was before
  -- with our key variable.
  NEW.id = key;

  -- The RECORD returned here is what will actually be INSERTed,
  -- or what the next trigger will get if there is one.
  RETURN NEW;
END;
$$ language 'plpgsql';

我有一个已经包含数据的表,我添加了一个名为pid的新列,是否有可能对其进行修改并使用函数调用作为默认值,以便所有先前的数据都获得一个简短的ID? / p>

1 个答案:

答案 0 :(得分:2)

假设您有一个表test

DROP TABLE IF EXISTS test;
CREATE TABLE test (foo text, bar int);
INSERT INTO test (foo, bar) VALUES ('A', 1), ('B', 2);

您可以在其中添加一个id列:

ALTER TABLE test ADD COLUMN id text;

并附加触发器:

DROP TRIGGER IF EXISTS unique_short_id_on_test ON test;
CREATE TRIGGER unique_short_id_on_test
    BEFORE INSERT ON test
    FOR EACH ROW EXECUTE PROCEDURE unique_short_id();

现在创建一个临时表temp,其结构与测试相同(但没有数据):

DROP TABLE IF EXISTS temp;
CREATE TABLE temp (LIKE test INCLUDING ALL);
CREATE TRIGGER unique_short_id_on_temp
    BEFORE INSERT ON temp
    FOR EACH ROW EXECUTE PROCEDURE unique_short_id();

test倒入temp

INSERT INTO temp (foo, bar)
SELECT foo, bar
FROM test
RETURNING *

产生类似:

| foo        | bar | id       |
|------------+-----+----------|
| A          |   1 | 9yt9XQwm |
| B          |   2 | LCeiA-P8 |

如果其他表在test表上具有外键引用,或者test必须保持在线状态, 可能无法删除test并将temp重命名为test。 相反,使用test中的id s更新temp是更安全的。

假设test有一个主键(为具体起见,我们称它为testid),然后 您可以使用以下方式使用test中的id s个来更新temp

UPDATE test
SET id = temp.id
FROM temp
WHERE test.testid = temp.testid;

然后,您可以放下temp表:

DROP TABLE temp;