The serial number might be just that, a serial number. That makes it is possible to trace back (via serial no) the person who made a special car / computer / whatever. So in case of a warranty claim, all other items produced by mr x can be checked "just ion case".
Timecard does not need a number, person A does B on date C hour D. Why would you need another timecard each day / week? 2010/6/11 Rich Shepard <[email protected]> > On Fri, 11 Jun 2010, Rich Shepard wrote: > > There must be a field in one of the postgres tables that changes each >> individual time card row to 'closed.' Doing so manually from the psql >> interface is fine with me as long as I know what table is involved. Then >> it's a matter of 'UPDATE <table> SET <status_column> = 'closed' where >> <timecard_number_column> in (<list of timecards>;'. >> > > Progress, I think. The jcitems table contains timecard information: > > project_id | integer | > parts_id | integer | not null > description | text | > qty | double precision | > allocated | double precision | > sellprice | double precision | > fxsellprice | double precision | > serialnumber | text | > checkedin | timestamp with time zone | > checkedout | timestamp with time zone | > employee_id | integer | > notes | text | > > but nothing that shows whether that serialnumber (I assume that's the > number > displayed with the timecard report) is open or closed. Would that be in the > acc_trans table? > > > Rich > _______________________________________________ > SQL-Ledger mailing list > [email protected] > http://lists.ledger123.com/mailman/listinfo/sql-ledger >
_______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
