[Collective-commerce] RE: PloneMall with external rdbms

[<jo...@fa...>]

Hi,

 First of all thx for all replies and for the warm welcome :)

 Their db is a Postgres one and the structure thats being set will be:

 - a view that will provide me the needed information regarding those
 items
 - an auxiliary table that will record all changes done to those items
 which I'll query in order to propagate those changes to teh site.

 This way I'll read the view once, create the objects (which will be
 based on plonemall's baseitem) and from then on - in order to keep them
 up to date - I'll query the aux table from time to time to check for
 changes. They will ensure that this aux table will reflect all changes.

 I also exposed my case in #plone and asked for opinions last Friday.
 Joel Burton - once again thx for your insight - also said that this
 approach seems to be a good one, attending to its circumstances, and
 that in this way I would have all Plone advantages being the only
 disadvantage the fact that I would need to create the scripts to keep
 all this synchronized. He advised to look into cron-wget to achieve
 this. So now I'm looking into this so I can set up a script+query combo
 that will get executed in a determined interval (each 12h/24h/etc).
 Again any pointers on this are welcome.

<snip>
Since your items don't exist as typical PloneMall items, you would have
to develop a way of feeding the item information into PloneMallCart. 
I'm thinking something along the lines of a DynamicCartItem that doesn't
rely on referencing a pre-defined PloneMall item.
</snip>

I might have forgot to mention that all records will become objects.
I'll subclass BaseItem to fit my needs thus allowing them to be added to
plonemall cart. I dont quite understand the bit about DynamicCartItem
but I think that extending BaseItem allows me to achieve this without
worrying about DynamicCartItem. Am I right? I want to avoid users
querying the external rdbms and it seems DynamicCartItem would rely on
queries targetting the db.

<snip>
 I'm in the process of completing a custom payment method for
 FirstData's YourPay Connect service using their LinkPoint Secure
 Payment Gateway (LSPG). [...] I'd be happy to share it with you.
</snip>

My findings related to what would need to be customized were based on
PloneMall beta2 version. WorldPay.py & TwoCheckout.py inside
PloneMallPayment folder are extremely similar. I concluded taht having a
MyPayment.py (with the obvious changes done) and then customizing both
config.py and CustomizationPolicy.py would do the trick. Besides this
files I would need to customize the template displaying the different
methods available - but this goes without saying ;)
When I searched the email archives I saw your post and I was hoping that
you would reply :) I would be grateful if you could help in any way
possible.

Thx xiru for the remark about SQLStorage. I "dropped" it because I wont
have write access to this info.

<snip>
Given the restrictions, I think his best approach would be to either A)
develop a synchronization process between a PloneMall item collection
and his RDBMS, or B) to create some sort of DynamicCartItem that is not
dependent on a pre-existing PloneMallItem and can be populated with data
obtained through a custom SQLMethod-based item catalog.  Either way,
it's going to require a lot of development.
</snip>

If i understood correctly option B) would be, more or less, to query the
db & create the needed objects on each purchase. Since this whole
purchasing process will have lots of searches option A) will be the best
one for my case.

Once again thx for all your help and once more any advice/input is
welcome :)

Joao
-- 
  
  jo...@fa...

-- 
http://www.fastmail.fm - Access your email from home and the web