I also agree with Alex, that version is an attribute, either of Job or of the Invoice. If you could have multiple invoices for a given version, then I'd see it be something along the lines of Project <->> Version <<->> Invoice (where an invoice could be for multiple versions of one or more projects).
Dave On Feb 5, 2011, at 8:40 AM, Theodore Petrosky wrote: > This is what I am looking for. However I still don't see my killed versions > in the invoice list and I changed the join as you mentioned. > > Of course, I could just create an invoice for a version that I kill (with all > zeros). That would end the issue (seems to be the easiest solution). But I > think I will try to think this through some more. > > Alex believes that my overall model may be wrong and that invoice should hang > on Job. I have to think that through and see if he is correct. I don't think > so but hey, I will give it my full attention. > > Ted > > --- On Sat, 2/5/11, David Avendasora <[email protected]> wrote: > >> From: David Avendasora <[email protected]> >> Subject: Re: inner join query help >> To: "Theodore Petrosky" <[email protected]> >> Cc: [email protected] >> Date: Saturday, February 5, 2011, 7:33 AM >> Hi Ted, >> >> I'm not 100% clear on exactly what you want. It sounds like >> you want to get a list of all Versions, regardless if they >> have an invoice or not. Is that correct? If so: >> >> In SQL you'd use an outer join if you wanted both Version >> and Invoice information in one result and you wanted to see >> Version information even if there were no Invoice to go with >> it. >> >> In WO, it is similar. You should model the Version -> >> Invoice relationship as a Left Outer join. This way you will >> get version records even if there are no corresponding >> Invoice records. >> >> Dave >> >> >> >> On Feb 5, 2011, at 7:07 AM, Theodore Petrosky wrote: >> >>> I could fairly easily do this in SQL with a join but i >> am lost in WO. >>> >>> I have two entities >> Version Invoice >>> >>> my full schema looks like: >>> >>> ParentCompany toMany >>> Client toMany >>> Project toMany >>> Job toMany >>> Version toOne >>> Invoice >>> >>> The Version may have many invoices because the version >> may be partially billed. >>> >>> in my Invoice report, I will see: >>> >>> Version 1 partial 01-01-2011 >>> Version 1 final 01-30-2011 >>> Version 3 final 01-05-2011 >>> >>> So what happened to version 2. The version was killed >> in production. there will be no version 2 invoice. (Let's >> also add that there could be a version 2.1 or even 2.1 >> subversion 1 and any of these could be killed.) >>> >>> Invoice only records the versions that are invoiced. >> so indeed there could be versions not included in the >> invoice list. >>> >>> Normally I would join the invoice list against the >> version list. Then I would have a complete list of invoices >> and versions. There would be no 'holes' where a version was >> killed. >>> >>> Version 1 partial 01-01-2011 >>> Version 1 final 01-30-2011 >>> Version 2 killed >>> Version 2.1 final 01-30-2011 >>> Version 3 final 01-05-2011 >>> >>> How to do this the WO way? >>> >>> I hope I am clear. >>> >>> Ted >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be >> ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com >>> >>> This email sent to [email protected] >>> >>> >> >> > > > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
