https://bugs.kde.org/show_bug.cgi?id=326733
Bug ID: 326733
Summary: collections: bundle pricing
Classification: Unclassified
Product: bodega
Version: unspecified
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: Server
Assignee: ase...@kde.org
Reporter: ase...@kde.org
CC: active@kde.org, terie...@gmail.com
bundle prices for collections should be shown in collection listings.
2 types of custom pricing should be assigned: automatic summation, publisher
bundle price, distributor bundle price.
publisher bundle price should only be available on collections of type
"publisher_bundle". these prices can be anything the publisher wishes, but all
assets in the collection must be owned by the same partner that owns the
collection.
distributor bundle price should only be be available on collections of type
"publisher_bundle" and all assets must appear in the same store and that store
must be owned by the publisher. this probably implies that collections can
optionally have a store associated with them.
a trigger should enforce this rule.
the final price of the collection would be:
(publisher_bundle && publisherPrice ? publisherPrice : sum(assets.basePrice)) *
(distributor_bundle && distributor_markup ? distributor_markup : storeMarkup)
the prices *could* be cached per-store and updated whenever the collection, the
assets or the store changes (some existing), but this may well be overkill.
measuring with `explain analyze` on the production db dataset will tell if this
added complexity is at all necessary.
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Active mailing list
Active@kde.org
https://mail.kde.org/mailman/listinfo/active
