Re: ProductCatalogId (and etc.) is not escaped/unescaped

2007-04-01 Thread Chris Howe
It is nice to have a primary key be descriptive, as it allows less programming thought and verification to go into an application. However that should be weighed against the dangers and limitations that convention may put on you. I don't think prodCatalogId or prodCategoryId, for that matter,

Re: ProductCatalogId (and etc.) is not escaped/unescaped

2007-03-31 Thread David E. Jones
BTW, if this is necessary there are things we can do in certain parts of the system, like using the 0x style encoding for UTF-8 characters and then decoding the parameters as they come in. For most pages in OFBiz this could even be done in generic places in the framework rather than

Re: ProductCatalogId (and etc.) is not escaped/unescaped

2007-03-31 Thread Shi Yusen
BTW, if this is necessary there are things we can do in certain parts of the system, like using the 0x style encoding for UTF-8 characters and then decoding the parameters as they come in. Yes, this will work. Some functions such as search may have to contain unicode characters in url

Re: ProductCatalogId (and etc.) is not escaped/unescaped

2007-03-31 Thread Shi Yusen
Hi Jonathon, I'm curious why Product.productId isn't a meaningless neutral integer as prescribed by the Data Model book. Chris Howe described some issues caused by using the Product.productId under some circumstances, and they seems closely related to this. I think ProductId is not