James K. Lowden wrote...
On Wed, 29 Jan 2014 23:37:43 +0000
Simon Slavin <[email protected]> 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" column which can contain
'open', 'paid', and perhaps even other statuses like 'awaiting
payment'.
If closed jobs matter, it can also be nice to use separate tables
after they're closed (or before they're opened) for logical and
physical reasons.
Things that are closed usually have additional attributes e.g. the
close date, by whom, and why.
Because history tends to grow (in a useful database) over time in a
one-table solution active rows become outnumbered by inactive ones.
But, yeah, maybe two tables. Not a million!
Thanks everyone for the help. The problem that I have is that I have
projects that have tasks. For example:
project 1
task 1 - File Processing/language de
task 2 - File Processing/language es
task 3 - File Processing/language it
task 4 - Translation/language de
task 5 - Translation/language es
task 6 - Translation/language it
task 7 - Publishing/language de
task 8 - Publishing/language es
task 9 - Publishing/language it
project 2
task 10 - File Processing/language de
task 11 - File Processing/language es
task 12 - File Processing/language it
task 13 - Translation/language de
task 14 - Translation/language es
task 15 - Translation/language it
task 16 - Publishing/language de
task 17 - Publishing/language es
task 19 - Publishing/language it
and so forth. Each of these task have also open/closed as well as the
project. For example, task1 belongs to project 1. Once task 1 is complete,
then, it becomes complete or closed, but task 2 may still be open. After
task 1 is closed, then, task 4 starts rolling and so forth. Also, each tasks
must have an uniqueID that task has a vendor and has a vendor charge against
it, so it needs to have an specific ID for the vendor to charge against it
and we have a unique trace of that task. We also must keep finances based
on projects, as well as task, so these tasks must also be connected to a
ProjID.
I know I have a lot of work to do, but, this indexing are helping a lot.
Thanks for your loving support. :-)
josé
_______________________________________________
sqlite-users mailing list
[email protected]
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
