14 09:09
>To: General Discussion of SQLite Database
>Subject: Re: [sqlite] Keeping Track of Records of IDs in one table.
>Possible?
>
>There is a problem in the first group of SQL statements. The coffee
>hadn't
>set in, and I always find crap on a reread-after-submission. S
There is a problem in the first group of SQL statements. The coffee hadn't
set in, and I always find crap on a reread-after-submission. Should read as
follows:
Previously: create table Tasks (TaskID INTEGER PRIMARY KEY AUTOINCREMENT,
fkProjectID integer, TaskID integer, TaskName char, Completed B
Wow! thanks for this. I have to read it slowly to capture the
understanding of some of the syntax. But this is great! thanks.
Stephen Chrzanowski" wrote...
Untested and only from the SQL compiler in my brain -- This compiler is
known to have a few bugs -- It may also be too late to go u
Untested and only from the SQL compiler in my brain -- This compiler is
known to have a few bugs -- It may also be too late to go use this, so this
might be something to look at if you plan on upgrading;
This is the first way I'd do it;
create table Projects (ProjectID INTEGER PRIMARY KEY AUTOINC
James K. Lowden wrote...
On Wed, 29 Jan 2014 23:37:43 +
Simon Slavin wrote:
By the way, once you have this working I would suggest (from my
experience) that you change your database design a little. Instead
of having a table containing just your open jobs, have a table
containing all jo
Simon Slavin wrote...
On 29 Jan 2014, at 10:42pm, jose isaias cabrera
wrote:
The tables are created this way:
CREATE TABLE OpenProjects (id integer primary key, ProjID integer,
createDnT, unique(id));
CREATE TABLE OpenJobs (id integer primary key, ProjID integer, Task,
unique(id));
Tha
On Wed, 29 Jan 2014 23:37:43 +
Simon Slavin wrote:
> By the way, once you have this working I would suggest (from my
> experience) that you change your database design a little. Instead
> of having a table containing just your open jobs, have a table
> containing all jobs, and add a "status"
On 29 Jan 2014, at 10:42pm, jose isaias cabrera wrote:
> The tables are created this way:
> CREATE TABLE OpenProjects (id integer primary key, ProjID integer, createDnT,
> unique(id));
> CREATE TABLE OpenJobs (id integer primary key, ProjID integer, Task,
> unique(id));
Thank you for this inf
, January 29, 2014 5:42 PM
To: General Discussion of SQLite Database
Subject: [sqlite] Keeping Track of Records of IDs in one table. Possible?
Greetings!
I have two tables: OpenProjects and OpenJobs. OpenJobs have jobs that
belong to one unique project (ProjID). OpenProjects are projects that
Greetings!
I have two tables: OpenProjects and OpenJobs. OpenJobs have jobs that
belong to one unique project (ProjID). OpenProjects are projects that have
one project fathers a bunch of jobs. The design below is found in a localDB
on the user's PC and also on a SharedDB file in a server t
10 matches
Mail list logo
