To do a better job, I’d need to see the data dictionary – eg to understand what
capacity means. Is it the capacity of a model? Ok, but what about contact
info for a model? Is this really the contact info of the plant?
But this is what I’d do
[cid:image002.png@01CAF33E.5FD30FB0]
Mfg – design
On 05/14/10 13:28, Trinath Somanchi wrote:
yes... But attribute of this table asl has an instance .. that two year
of releases are possible
also... I'm speaking of a very trivial case.
it doesnt multiplies the multitude of table.
it makes no problems with the "joins of ALL the tables"
--
Sent
On Friday 14. May 2010 10.42.17 Trinath Somanchi wrote:
> Hi All,
[snipped]
> This way the data in the table is tree structured. Also A single
> manufacturer has all mode of vehicles. I'm in my way to design this DB for
> use in PgSQL. But for a vast data, data retrieval is a very costly task
> (Jo
yes... But attribute of this table asl has an instance .. that two year of
releases are possible
also... I'm speaking of a very trivial case.
On Fri, May 14, 2010 at 2:44 PM, silly sad wrote:
> On 05/14/10 12:42, Trinath Somanchi wrote:
>
>> Hi All,
>>
>> I have Tree structured database to maint
On 05/14/10 12:42, Trinath Somanchi wrote:
Hi All,
I have Tree structured database to maintain.
Its as follows.
Vehicles
u r talking about a single entity vehicles
it is very common to represent a single entity with a single table
and IF u also have to have an entity "class of vehicles"
u r
Hi All,
I have Tree structured database to maintain.
Its as follows.
Vehicles
|__> Two Wheelers
|__> Manufacturer
|__> Name of Manufacturer
|__> Year of make.
|__> Manuf. Plant.
|__> Model.
|__> Model Name
