We aren't, as far as I'm aware, planning on doing anything with a password
at the moment. User login information is only here for the future, and I'm
currently creating the 'default' user with a hash of 'default' for the
password field, but it won't really be used anywhere.


On Thu, Jan 30, 2014 at 2:05 AM, seanblue <notifications@github.com> wrote:

> In SQL/initializeDatabase.sql:
>
> > +    name VARCHAR(255) NOT NULL,
> > +    state BLOB,
> > +    created DATETIME,
> > +    createdBy INT,
> > +    lastModified DATETIME,
> > +    lastModifiedBy INT,
> > +
> > +    UNIQUE (name),
> > +    FOREIGN KEY (createdBy) REFERENCES user(id),
> > +    FOREIGN KEY (lastModifiedBy) REFERENCES user(id)
> > +);
> > +
> > +CREATE TABLE user(
> > +    id INTEGER PRIMARY KEY ASC,
> > +    login VARCHAR(50) NOT NULL,
> > +    password VARCHAR(32) NOT NULL,
>
> We don't plan to actually validate a password, right? In which case we're
> probably just storing a hashed string "password" or something like that. Is
> that remotely accurate?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/KSHSK/WAVED/pull/49/files#r9297226>
> .
>