My answers interspersed below (and yes, I have read his follow up reply
that had additional information)
Giulio <[EMAIL PROTECTED]> wrote on 10/11/2004 05:44:43 AM:
> Hi all,
>
> I have some doubts about how to implement this kind of scenario:
>
> I have a table of elements in cronological ord
Il giorno 11/ott/04, alle 11:53, [EMAIL PROTECTED] ha scritto:
I think you need to explain what kind of SELECTs you want to do, and
what
results you expect.
you're right, I'll try to explain it better
I'm working on a system that must keep track of all the music
broadcasted by a tv,
so, let's c
I think you need to explain what kind of SELECTs you want to do, and what
results you expect. How do you expect to get results from a SELECT which
returns hits in both the B and C tables? If you expect to do this, then
the D table is probably your correct answer. Do you really need a rec_type
f
Hi all,
I have some doubts about how to implement this kind of scenario:
I have a table of elements in cronological order, let's call it table A:
for every A element, I have a number of elements ordered on a
progressive number.
This could be a simply one-to-many relation, where I can handle a list
