Re: Real world issue: How to "split" queries in presence of record replication and replication sensitive aggregate functions ?
Date: 16 Sep 2006 09:37:44 -0700
Message-ID: <1158424664.022587.300380_at_m73g2000cwd.googlegroups.com>
pamelafluente_at_libero.it wrote:
> Marshall ha scritto:
> . I'm afraid
> > you'll need to reread the wikipedia entry with this in mind.
>
> Thanks, I will.
You are entirely welcome.
> Ok I will produce a couple of simple examples using Northwind, which
> is quite common so that we do not have to do a scheme ex novo.
>
> I will keep simple (Just 1 table is useless, because in such a case
> no value duplication can occur) .
I'm sorry, but you're still no there yet. If you can't do it with one table, then try two. If you can't do it with two columns, try three. The example really needs to be as small as possible. When I say "as small as possible" I literally mean that the removal of even one table, or one column, or even just one row would not demonstrate the issue any more.
> For table relationships see: Northwind
No thanks. If you use Northwind, you're making me have to go find it, then find a dbms that can load it, then load it, then look at it, before I can even parse your question. I'm squeezing question-answering on this forum in between raising kids, having a full time job, etc. and that's just too much work. This is why asking the minimal question is so important. Don't make me go do extra work just so I can answer your question.
The following is quite blunt, but it could help you a lot:
How To Ask Questions The Smart Way
Marshall Received on Sat Sep 16 2006 - 18:37:44 CEST