[adminer-tracker] [ adminer-Bugs and Features-3609741 ] Unique key not dumped correctly

[SourceForge.net <no...@so...>]

Bugs and Features item #3609741, was opened at 2013-04-01 15:11
Message generated for change (Tracker Item Submitted) made by grim-fandango
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1127745&aid=3609741&group_id=264133

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: SQLite
Group: 3.6.3
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Grim Fandango (grim-fandango)
Assigned to: Jakub Vrána (jakubvrana)
Summary: Unique key not dumped correctly

Initial Comment:
Create table with:

-- Adminer 3.6.3 SQLite 3 dump

DROP TABLE IF EXISTS "sqlite_sequence";
CREATE TABLE sqlite_sequence(name,seq);

DROP TABLE IF EXISTS "posts";
CREATE TABLE "posts" (
  "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT,
  "thread_id" integer NOT NULL,
  "url" text NOT NULL,
  "body" text NOT NULL,
  "links" text NOT NULL,
  "user" text NOT NULL,
  FOREIGN KEY ("thread_id") REFERENCES "thread" ("id") ON DELETE NO ACTION ON UPDATE NO ACTION
);


DROP TABLE IF EXISTS "threads";
CREATE TABLE "threads" (
  "id" integer NOT NULL PRIMARY KEY AUTOINCREMENT,
  "title" text NOT NULL,
  "url" text NOT NULL
);


-- no such table: 

-- 

Then goto table 'posts'  create a unique key over 'url'.

Notice that here no warning is generated about incompatibility with NOT NULL.

Now try to dump table posts and you will see that unique is not respected as it conflicts with NOT NULL.

No warning or anything is generated.

Ideally a warning or error should be given in both situation.s

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1127745&aid=3609741&group_id=264133