Not easy to visualize...
Assuming your access path to the data is based on students, then you would serialize your college data as a column in the student's table.
You need to forget your relational way of thinking.
You need to think not just in terms of data, but how you intend to use the data. If you have an orthogonal use case you will have to get creative... ;-)
Sent from a remote device. Please excuse any typos...
On Feb 1, 2012, at 1:51 AM, [EMAIL PROTECTED] wrote:
> Suppose i have a relationship 1 to N, for example
> Student , College.
> Student Attributes:
> College attributes:
> Suppose that i have a program which read students and Exams from a plain text file.
> And on this file i have duplicated Colleges and Duplicated Studens.
> Like in denormalized tabels:
> you see i have to check in this case always that in my normalized db, i have still not inserted in the Table College
> 2 times the key 1, how can i solve this in Hbase ? i mean if i have 1000.. tables and rows i dont want check
> for every Primary Key and then for every Fk if it was inserted ok ?
> how can i solve that ?
> [EMAIL PROTECTED]
> Inviato con Sparrow (http://www.sparrowmailapp.com/?sig)