Could you give a high level overview of what is going on here and how
you were able to implement the Parent -> Child model in a single form?
Following your links, I wasn't able to discern where/if the input form
was actually accepting values for multiple tables.
I need similar functionality to Portly, and don't really want to go the
iframe route.
Specifically I need to show the 'children' of a table in the same input
form as the parent.
Thanks
Geoff
In any case, I don't think this is going to work for my case, as a
simply storing mutltiple strings in a single field isn't what I need.
I have another table with ~20 columns.. nutrition information
specifically.
Two types of things have nutrition information, recipes and basic foods.
Basic foods are simple
Name | Type | Nutrition Table Ref
Recipes are quite a bit more complex, but also need to reference the
Nutrtion Table.
Maybe I am just structuring this wrong entirely and should keep the
Nutrition information in the two tables? Since I will have to be
querying the Nutrition table to get both basic Foods and Recipes back, I
think it makes sense to keep the Nutrition information separate.
There is only a one to one correspondence between nutrition information
and another row.. the same row in the nutrition table won't be
referenced by two different rows in either the recipe table or the
basic_foods table.
I hope that this explanation makes clear why I believe your list:string
solution (which is great and I will use else where in this app) does not
solve this particular problem.
Thanks
Geoff
On Wed, 2010-09-08 at 13:27 -0700, mdipierro wrote:
Of course this does not really solve an 'address' issue if an address is
more than one field, which is the case for both myself and the original
poster.
In any case, that is a wonderful widget!
Best,
Geoff