The current bookshelves table looks like this :
CREATE TABLE public.bookshelves (
pk integer NOT NULL,
bookshelf text NOT NULL,
downloads integer DEFAULT 0 NOT NULL,
release_date date DEFAULT '1970-01-01'::date NOT NULL,
tsvec tsvector,
CONSTRAINT bookshelves_bookshelf_check CHECK ((bookshelf <> ''::text))
);
(with a many-to-many relationship to books.)
the bookshelf column is overloaded - text has been use to denote two different types of bookshelves while also serving as bookshelf title.
this has led to kludge upon kludge. to provide the needed presentation flexibility.
there should be a type column and also a descriptions column to allow shorter, more flexible titles and while also providing more useful descriptions.
gutenbergtools/autocat3#226
The current bookshelves table looks like this :
CREATE TABLE public.bookshelves (
pk integer NOT NULL,
bookshelf text NOT NULL,
downloads integer DEFAULT 0 NOT NULL,
release_date date DEFAULT '1970-01-01'::date NOT NULL,
tsvec tsvector,
CONSTRAINT bookshelves_bookshelf_check CHECK ((bookshelf <> ''::text))
);
(with a many-to-many relationship to books.)
the bookshelf column is overloaded - text has been use to denote two different types of bookshelves while also serving as bookshelf title.
this has led to kludge upon kludge. to provide the needed presentation flexibility.
there should be a type column and also a descriptions column to allow shorter, more flexible titles and while also providing more useful descriptions.
gutenbergtools/autocat3#226