Login | Register
My pages Projects Community openCollabNet

propel
Reply to message

* = Required fields
* Subject
* Body
Attachments
Send reply to
Topic
Author (directly in email)
Please type the letters in the image above.

Original message

Author Ron Rademaker <r.rademaker@virtualbuilding.nl>
Full name Ron Rademaker <r.rademaker@virtualbuilding.nl>
Date 2007-11-09 04:02:16 PST
Message Hi Hans,

Hans Lellelid wrote:
> Actually, one thing that would be *very* helpful is if you could get
> some feedback from your developers on what they really need in the new
> Criteria -- e.g. which queries they are trying but cannot build in
> current version -- so that we can add those to the list.
>
> Thanks,
> Hans
>
> --------------------​--------------------​--------------------​---------
> To unsubscribe, e-mail: dev-unsubscribe@prop​el.tigris.org
> For additional commands, e-mail: dev-help at propel dot tigris dot org
>
>
>

I'll send them all an e-mail to tell me their wishes. I think it'll be a
lot of basic things though, that can actually be accomplished with
Propel but are though of as being hacky (like manually adding select
columns for two tables if you want all results when joining two tables)
or clumsy (like requiring separate criterions to create something like a
< 5 or a > 10). Anyway, I'll get back to you on this next week.

Something very different. I got some time reserved next week to do some
propel development (such time slots are rare for me), first order of
business is gonna be to upgrade our propel 1.3 branch to the latest in
propel svn. But I think I'll have some time left to work on a new
feature, one I call triggerBackup. I was wondering if this would be a
feature people would like in propel and if yes, where should I commit
unstable code (I expect version 1 to support only PostreSQL and MySQL).
The idea is that you can add triggerBackup='true' in your schema to a
<table> node. This would cause propel to generated the table twice, once
the way you defined it (primary table), again as <tablename>_backup with
extra columns <tablename>_id (foreign key to the primary table) and date
(the secondary table). Furthermore, it would create a SQL trigger on the
primary table that would add a record with all the information in the
deleted / updated record to the secondary table. Hope this short
explanation makes sense.

Ron