In terms of structuring your db there are 2 main types of relationships, "owned" and "unowned". Unowned relationships are similar to relational db's where you store a key in the related table, whereas owned relationships are stored directly in the parent table as an attribute list. Owned relationships are easier to work with in the GAE and are very suitable for things like tags where you don't need a master instance of that record.
In terms of structuring your cfc's, it would be similar whichever storage structure you choose - probably composing an array of the related cfc's within an attribute of it's parent. There is a lot of discussion, theories and best practices on how to model your data in the datastore given your specific situation. I'm usually against answering questions by referring people to google, but in this case there are so many permutations that depend on your specific use-case that it makes sense. For example, even if you are actually storing tags, or similar data, you also have to consider that there is a limit on the number of owned objects you can have (is it 250?). I would love to hear updates on what you are finding out and choosing to do. I'm no expert and just threw out what I know to get the discussion started :) Cheers, Baz -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
