Status of archetypes.sqlalchemystorage and collective.lead (tpc branch)

3 Messages Forum Options Options
Embed this topic
Permalink
Rudá Porto Filgueiras
Status of archetypes.sqlalchemystorage and collective.lead (tpc branch)
Reply Threaded More
Print post
Permalink
Hi,

I'm interest in know if there is some people using
archetypes.sqlalchemystorage in production or some in going projects.
Since last month I began some investigation of packages use as infra
structure to develop a product to turn easy map AT objects to
relational databases.

My use case is:

1) map fileds to sql types and create custom sqlalchemy types to help
2) map reference fields and referenceable API to especialized sql
table object and mapper
3) map files and images to file system (I'm not yet decide which
existing package to use)

Now I have some code and tests working for 1 and 2, but get trouble
with archetypes.sqlalchemystorage that depends on especifc version of
collective.lead:
https://svn.plone.org/svn/collective/collective.lead/branches/sqlalchemy-0.4

This version don't support transaction.savepoint and have some unique
event dispatch used by archetypes.sqlalchemystorage.
These events are:

class SessionFlushedEvent(SessionEvent):
    implements(ISessionFlushedEvent)

class BeforeSessionFlushEvent(SessionEvent):
    implements(IBeforeSessionFlushEvent)

Why these events don't get merged into collective.lead trunk?
There is any other aprouch (hooks) to be used by
archetypes.sqlalchemystorage by this porpouse:

I also check another collective.lead branch that supports savepoints:
http://svn.plone.org/svn/collective/collective.lead/branches/elro-tpc/
Is it the base for collective.lead 2.0 right? What is it status? Beta, Alpha?

Finally, I've made some patches to make archetypes.sqlalchemystorage
compatible with Zope 2.9 and to deal with problems about BaseUnit
fields that don't like None values.
I now have time (in this project) to help in improve
archetypes.sqlalchemystorage to be compatible with new versions of
collective.lead and involve it.

I'm also write SQLAlchemy types to map DateTimeField and LinesField
and a "generator" that creates Mapper class and Table class
automatically from a given AT class and monkey patch Referenceable API
(for a given class) and ReferenceField.set (for a given ReferenceField
instance).  This code will in future be released as open source, but
some parts can be (or not) incorporated to
archetypes.sqlalchemystorage.

Regards,

--
=====================================
Rudá Porto Filgueiras
Weimar Consulting

Plone, Django, Zope 3, Grok hosting
http://www.pytown.com
=====================================

_______________________________________________
Product-Developers mailing list
Product-Developers@...
http://lists.plone.org/mailman/listinfo/product-developers
Laurence Rowe
Re: Status of archetypes.sqlalchemystorage and collective.lead (tpc branch)
Reply Threaded More
Print post
Permalink
Rudá Porto Filgueiras wrote:
Now I have some code and tests working for 1 and 2, but get trouble
with archetypes.sqlalchemystorage that depends on especifc version of
collective.lead:
https://svn.plone.org/svn/collective/collective.lead/branches/sqlalchemy-0.4

This version don't support transaction.savepoint and have some unique
event dispatch used by archetypes.sqlalchemystorage.
These events are:

class SessionFlushedEvent(SessionEvent):
    implements(ISessionFlushedEvent)

class BeforeSessionFlushEvent(SessionEvent):
    implements(IBeforeSessionFlushEvent)

Why these events don't get merged into collective.lead trunk?
There is any other aprouch (hooks) to be used by
archetypes.sqlalchemystorage by this porpouse:
This functionality would be better implemented with a MapperExtension rather than an event fired from a SessionExtension.

I also check another collective.lead branch that supports savepoints:
http://svn.plone.org/svn/collective/collective.lead/branches/elro-tpc/
Is it the base for collective.lead 2.0 right? What is it status? Beta, Alpha?
It ended up as zope.sqlalchemy. I merged a zope.sqlalchemy dependency into trunk but broke the persistent database configuration pattern in the process. I don't have an immediate need for a new collective.lead version, so will probably refactor it again based on z3c.saconfig before making a 2.0 release.

Laurence
Rudá Porto Filgueiras
Re: Status of archetypes.sqlalchemystorage and collective.lead (tpc branch)
Reply Threaded More
Print post
Permalink
On Fri, Aug 1, 2008 at 1:32 PM, Laurence Rowe <l@...> wrote:

>
>
> Rudá Porto Filgueiras wrote:
>>
>> Now I have some code and tests working for 1 and 2, but get trouble
>> with archetypes.sqlalchemystorage that depends on especifc version of
>> collective.lead:
>> https://svn.plone.org/svn/collective/collective.lead/branches/sqlalchemy-0.4
>>
>> This version don't support transaction.savepoint and have some unique
>> event dispatch used by archetypes.sqlalchemystorage.
>> These events are:
>>
>> class SessionFlushedEvent(SessionEvent):
>>     implements(ISessionFlushedEvent)
>>
>> class BeforeSessionFlushEvent(SessionEvent):
>>     implements(IBeforeSessionFlushEvent)
>>
>> Why these events don't get merged into collective.lead trunk?
>> There is any other aprouch (hooks) to be used by
>> archetypes.sqlalchemystorage by this porpouse:
>>
>>
>
> This functionality would be better implemented with a MapperExtension rather
> than an event fired from a SessionExtension.
Thanks, I will investigate how to do it ;-)

>>
>> I also check another collective.lead branch that supports savepoints:
>> http://svn.plone.org/svn/collective/collective.lead/branches/elro-tpc/
>> Is it the base for collective.lead 2.0 right? What is it status? Beta,
>> Alpha?
>>
>>
>
> It ended up as zope.sqlalchemy. I merged a zope.sqlalchemy dependency into
> trunk but broke the persistent database configuration pattern in the
> process. I don't have an immediate need for a new collective.lead version,
> so will probably refactor it again based on z3c.saconfig before making a 2.0
> release.
I follow all discussion in zope-dev about zope.sqlalchemy and at this
moment I'm testing a modified branch of archetypes.sqlalchemystorage
to incoporate events and use zope.sqlalchemy with a custom Database
object much like collective.lead.

I also investigate z3c.saconfig but it has some tests that don't run
against Zope 2.9 and it depends on localsite support.
Plone 2.5 with Five 1.4.4 can be configurated to have local utilities rigth?

Thanks again by feedback.

> Laurence
> --
> View this message in context: http://n2.nabble.com/Status-of-archetypes.sqlalchemystorage-and-collective.lead-%28tpc-branch%29-tp663084p664571.html
> Sent from the Product Developers mailing list archive at Nabble.com.
>
>
> _______________________________________________
> Product-Developers mailing list
> Product-Developers@...
> http://lists.plone.org/mailman/listinfo/product-developers
>


--
=====================================
Rudá Porto Filgueiras
Weimar Consulting

http://python-blog.blogspot.com

Plone, Django, Zope 3, Grok Hosting
http://www.pytown.com
=====================================

_______________________________________________
Product-Developers mailing list
Product-Developers@...
http://lists.plone.org/mailman/listinfo/product-developers