xorm reverse doesn't support postgresql inet type #3

Open
opened 2020-03-01 02:30:05 +00:00 by lunny · 0 comments
Owner

Moved from xorm/xorm#1330

When I use xorm reverse tools to reverse my database tables, It occured that "[Error] reverse.go:160 Unknown colType: inet", not support postgresql inet?

-- Table: public.logs

-- DROP TABLE public.logs;

CREATE TABLE public.logs
(
    uid uuid NOT NULL DEFAULT uuid_generate_v4(),
    meta_data jsonb,
    created_at timestamp with time zone,
    updated_at timestamp with time zone,
    deleted_at timestamp with time zone,
    created_user_uid uuid DEFAULT uuid_nil(),
    updated_user_uid uuid DEFAULT uuid_nil(),
    comment text COLLATE pg_catalog."default",
    ip inet,
    client_refer uuid,
    src_addr inet,
    CONSTRAINT logs_pkey PRIMARY KEY (uid)
)
WITH (
    OIDS = FALSE
)
TABLESPACE pg_default;

ALTER TABLE public.logs
    OWNER to tsl;
Moved from https://gitea.com/xorm/xorm/issues/1330 When I use xorm reverse tools to reverse my database tables, It occured that "[Error] reverse.go:160 Unknown colType: inet", not support postgresql inet? ```sql -- Table: public.logs -- DROP TABLE public.logs; CREATE TABLE public.logs ( uid uuid NOT NULL DEFAULT uuid_generate_v4(), meta_data jsonb, created_at timestamp with time zone, updated_at timestamp with time zone, deleted_at timestamp with time zone, created_user_uid uuid DEFAULT uuid_nil(), updated_user_uid uuid DEFAULT uuid_nil(), comment text COLLATE pg_catalog."default", ip inet, client_refer uuid, src_addr inet, CONSTRAINT logs_pkey PRIMARY KEY (uid) ) WITH ( OIDS = FALSE ) TABLESPACE pg_default; ALTER TABLE public.logs OWNER to tsl; ```
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: xorm/reverse#3
No description provided.