| Re: Need help accessing the key array. [message #185454 is a reply to message #185452] |
Tue, 01 April 2014 02:16   |
Richard Damon
Messages: 58
Registered: August 2011
Karma:
|
Member |
|
|
On 3/31/14, 8:55 PM, Denis McMahon wrote:
> On Mon, 31 Mar 2014 07:37:19 -0400, Jerry Stuckle wrote:
>
>> I see no need for arrays or json objects in a database here. Or a graph
>> database, for that matter.
>
> Agreed. A table with three elements per row, namely animal, colour, rate,
> keyed on the combination of animal and colour.
>
> Or possible 3 tables:
>
> animals: animal_name* | animal_id
>
> colours: colour* | colour_id
>
> rates: animal_id* | colour_id* | rate
>
> Where * indicates the field(s) that make the PK for the table, but I
> suspect that's overkill for the task as described so far.
>
I would probably make animal_id and colour_id the PK for those tables,
as that is what other tables are going to refer to via Foreign Keys.
animal_name and colour would be indexed, and possible unique.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]