On Mon, Mar 8, 2010 at 10:16 AM, Scott Marlowe wrote:
> On Sun, Mar 7, 2010 at 11:31 PM, Allan Kamau wrote:
>> On Mon, Mar 8, 2010 at 5:49 AM, Scott Marlowe
>> wrote:
>>> On Sun, Mar 7, 2010 at 1:45 AM, Allan Kamau wrote:
Hi,
I am looking for an efficient and effective solution to el
On Sun, Mar 7, 2010 at 11:31 PM, Allan Kamau wrote:
> On Mon, Mar 8, 2010 at 5:49 AM, Scott Marlowe wrote:
>> On Sun, Mar 7, 2010 at 1:45 AM, Allan Kamau wrote:
>>> Hi,
>>> I am looking for an efficient and effective solution to eliminate
>>> duplicates in a continuously updated "cumulative" tra
On Mon, Mar 8, 2010 at 5:49 AM, Scott Marlowe wrote:
> On Sun, Mar 7, 2010 at 1:45 AM, Allan Kamau wrote:
>> Hi,
>> I am looking for an efficient and effective solution to eliminate
>> duplicates in a continuously updated "cumulative" transaction table
>> (no deletions are envisioned as all non-r
On Sun, Mar 7, 2010 at 1:45 AM, Allan Kamau wrote:
> Hi,
> I am looking for an efficient and effective solution to eliminate
> duplicates in a continuously updated "cumulative" transaction table
> (no deletions are envisioned as all non-redundant records are
> important). Below is my situation.
I
Hi,
I am looking for an efficient and effective solution to eliminate
duplicates in a continuously updated "cumulative" transaction table
(no deletions are envisioned as all non-redundant records are
important). Below is my situation.
I do have a “central” transaction table (A) that is expected to
On Fri, 24 Mar 2000, sheila bel wrote:
> Hi everyone,
>
> I have a generel SQL question. What is the best way to
> avoid inserting duplicate tuples in a table ?
> using constraints ? Please refer me to a resource about
> this topic.
primary key -- which you can say is also a contraint.
of cour
Hi everyone,
I have a generel SQL question. What is the best way to
avoid inserting duplicate tuples in a table ?
using constraints ? Please refer me to a resource about
this topic.
Thank you for your time,
-Sheila
__
Get Your Private, Free Ema
