On Jun 4, 2007, at 8:47 PM, Thomas Wood wrote:
Both the download_id in Artwork and Collection where suppose to represent the file associated with them, but now that I think of, it is better to have a field in download table to associate it with the artwork and other to associate it with the collection. And yeah, a name field is missing in both. The allow_in_collection field is suppose to represent if the author of the work allows it to be used in the construction of a collection. I think authors should say if they want their works to be used in collections. We can add both fields, and during the submission fill in that information. Ok, we can do that, but I still think we should have a list of resolutions, in case we want to do a search of wallpapers by resolution. True, that's why FAQ's have an type_id associated. I also thought categorize FAQ's. Doing so we can have a category for each work type.
The only job I predicted to this flag was to say if that category was a contest or not. We can represent it like 0:not contest; 1:contest. But in case some other idea comes up, we can define new flags to represent new options. Ok Done
I like the one in the link. There just one thing I would prefer to use: field naming. It says we should name fields like <table_name>_field i.e. product_name I prefer to use just name, since I queries we can use product.name to refer to that field. What do you think?
Regards, Bruno Santos __
|