View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004290 | OXID eShop (all versions) | 4.07. Source code, Test | public | 2012-07-30 11:00 | 2012-12-10 13:44 |
| Reporter | b.hasis | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Summary | 0004290: oxfield2shop views are inconvenient | ||||
| Description | They are no views for subshop, just language dependent views... So if i try to get a Price by using getViewName( 'oxfield2shop' ); i have to select the right shop by using where in the sql statement. | ||||
| Tags | No tags attached. | ||||
| Theme | Both | ||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| has duplicate | 0004289 | closed | jurate.baseviciene | oxpricea, oxpriceb and oxpricec in the articleviews shows prices of supershop |
|
|
Reminder sent to: b.hasis Hi, Could you please tell us Use Case how you want to use this views? |
|
|
Hi, i want to get a very simple list of All-Article an here a-c prices. So because of the performance i dont want to load any kind if oxarticle objects or oxarticlelists. I tried it also over the article views (see this https://bugs.oxid-esales.com/view.php?id=4289). My expected results of using getViewName( 'oxfield2shop' ); in a Mall was a list of articles with here a-c prices in this Mall, and not all a-c prices for all shops. I have to filter the mall in my query, thats not difficult, but for consistent of the views i think the views have to be uniform at all. Or is there a reason why not, in this case, that i miss? regards |
|
|
oxfield2shop - table is not regular multi-shop table (have no OXSHOPINCL, OXSHOPEXCL) so not needs for view per shop. simply use shopId check in where part in queries |
