[Date Prev][Date Next][Thread Prev][Thread Next][Interchange by date
][Interchange by thread
]
[ic] consignment users
Quoting cfm@maine.com (cfm@maine.com):
> On Wed, Aug 14, 2002 at 11:39:37AM -0400, Bill Carr wrote:
> > On Wed, 2002-08-14 at 10:20, cfm@maine.com wrote:
> > > On Wed, Aug 14, 2002 at 10:04:07AM -0400, Bradley Glonka wrote:
> > > > Hi,
> > > >
> > > > We'd like to use one interchange store to manage multiple users who sell
> > > > items on consignment. Ideally these users would have the following
> > > > functionality.
> > > >
> > > > - Login via admin interface and only manipulate
> > > > items that belong to them. Also they'll need
> > > > to add new items.
> > > >
> > > > - Receive orders that belong to them via email or
> > > > admin interface.
> > > >
> > > > - Have a URL, search sting, page they could give to
> > > > their client to show only their items. We tried
> > > > using category or product group, but we need those
> > > > fields for overall organization of the site.
> > > >
> > > > - Reports based on consignee.
> > > >
> > > > Can anyone clue me in on how to achieve any of these items?
> > >
> > >
> > > It can be done but it is a lot of work. Just consider, for example,
> > > how you will teach these consignment users to use encrypted email.
> > > You'll want entirely "virtual" catalogs. All your items need
> > > enterprise keys because skus will no longer be unique, etc....
> > I don't know what an enterprise key is but you could add a 'storeid'
> > column to any table that uses a sku column.
>
> you will want to index products UNIQUE KEY (storeid,sku)
> but you'll also want a simple unique key for every record, not
> just products, otherwise you end up storeid=adsf AND sku=asfa
> in every table just to do a simple update. You are going to end up
> with other tables to make it all virtual. enterprise keys just
> mean it's a key across the entire "enterprise".
>
> I've been wondering if a database that supports views might be
> able to build an arbitrary number of views usable as per store
> database tables on the fly. Haven't had a chance to look at it.
> That seems much cleaner than doing the AND storeid everywhere.
>
I would think so. It would not be difficult, especially as Stefan gets
his new Vend::Table::Shadow more functional.
--
Mike Heins
Perusion -- Expert Interchange Consulting http://www.perusion.com/
phone +1.513.523.7621 <mike@perusion.com>
Nature, to be commanded, must be obeyed. -- Francis Bacon