Sorry for the lack of explanation. Again: I have to model a bill table. The bill have 20 fields. But for each field we have: *registered* value, *billed *value and* total value.* So i've created an *bill* table with *20 *fields (representing the bill fields, like: consumption, demand, etc ), and a *bill_values* table (with *id*,*registered*,*billed *and *total*). I'll try to ilustrate: Bill Table *ID | eletricity_use | eletricity_demand_ | eletricity_traffic_use | eletricity_penalties *| etc ........ 1 101 102 103 104 *AND* Value Table *ID | Registered | Billed | Total* 101 120,00 150,12 102,36 102 130,00 150,12 102,36 103 150,00 150,12 102,36 104 110,00 140,12 102,36 better? Thanks! 2012/9/19 Jim Giner <jim.giner@xxxxxxxxxxxxxxxxxx> > On 9/19/2012 3:12 PM, Jim Giner wrote: > >> On 9/18/2012 8:52 AM, Bruno Sandivilli wrote: >> >>> Hi, i strugling to decide what is the best choice: >>> >>> I have a 15 row x 3 columns Flash DataGrid, it means, for each row i >>> have 3 >>> values. >>> To represent this in my Database, I could: >>> >>> >>> 1. Create 2 Tables : A Values table - with 3 columns ; and a Bill >>> table >>> (with 15 foreign keys, each one pointing to one row in the Values >>> table). >>> 2. Create one Table with 45 columns (15 fields * 3 values for each >>> field). >>> >>> I want to know, wich is the best choice? >>> To manage my query, now i have a SELECT with a thousand of leftJoins. >>> >>> This is the best choice? >>> >>> How could I run a query wich will give all results linked, like: >>> ( column_1_val_1, column_1_val_2, column_1_val_2, >>> column_2_val_1, column_1_val_2, column_1_val_3, >>> etc...) ? >>> >>> Thanks! >>> >>> I don't get it either. >> >> You have 15 rows with 3 cols each. So? Display them. Query them. Big >> deal. >> >> What is the real difficulty here? I'm not seeing it. >> >> (I don't read it as 15x3x3 - at least that's not what he said since he >> said 'for each row he has 3 values') >> > Continuing on - why is your visual structure at this point NOT the same as > your physical structure? I don't think you're telling us what your real > problem is here. We need more information. You have '15 row with 3 cols > each', ie, 'each row has 3 values'. So - your table has 15 records in it, > each with 3 columns. Add a key field to give each row an identity and > that's it. No? > > Sorry - but again - this post is not showing me a clear problem. > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >