• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: inner join query help
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: inner join query help


  • Subject: Re: inner join query help
  • From: David Avendasora <email@hidden>
  • Date: Sat, 5 Feb 2011 07:33:38 -0500

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@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
>

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: inner join query help
      • From: Theodore Petrosky <email@hidden>
References: 
 >inner join query help (From: Theodore Petrosky <email@hidden>)

  • Prev by Date: inner join query help
  • Next by Date: Re: inner join query help
  • Previous by thread: inner join query help
  • Next by thread: Re: inner join query help
  • Index(es):
    • Date
    • Thread