[EMAIL PROTECTED] wrote:
Quoting Daryl Richter <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
> Quoting Daryl Richter <[EMAIL PROTECTED]>:
>> It's hard to say without knowing more precisely what you are trying to
>> model, but I think this push you in the right direction:
>>
> Okay, but referenc
Quoting Daryl Richter <[EMAIL PROTECTED]>:
[EMAIL PROTECTED] wrote:
> Quoting Daryl Richter <[EMAIL PROTECTED]>:
>> It's hard to say without knowing more precisely what you are trying to
>> model, but I think this push you in the right direction:
>>
> Okay, but references between (output/input) a
[EMAIL PROTECTED] wrote:
> Quoting Daryl Richter <[EMAIL PROTECTED]>:
>
>> It's hard to say without knowing more precisely what you are trying to
>> model, but I think this push you in the right direction:
>>
[snipped old schema]
>
> Okay, but references between (output/input) and ACTIVITY table
Quoting Daryl Richter <[EMAIL PROTECTED]>:
It's hard to say without knowing more precisely what you are trying
to model, but I think this push you in the right direction:
-- This table takes the place of both SEND and BUY
create table activity(
id serial primary key,
prod
[EMAIL PROTECTED] wrote:
Ok,
But the problem is becouse the "buy" and "send" tables referencing with other
father table, wich is different.
I shoud not create a spent table to put the "buy" and "send" values
becouse the
entire database is more complex than it. look:
create table output(
id seria
Ok,
But the problem is becouse the "buy" and "send" tables referencing with other
father table, wich is different.
I shoud not create a spent table to put the "buy" and "send" values
becouse the
entire database is more complex than it. look:
create table output(
id serial primary key,
client integ
