AW: [jbpm-dev] Stabilizing DB schema

Heiko Braun hbraun at redhat.com
Tue May 26 11:34:22 EDT 2009


yes, but it needs to be coordinated.

On May 26, 2009, at 4:59 PM, Bernd Rücker wrote:

> Isn't it, that we should do all now which might make sense? Since
> afterwards we cannot change it anymore?
>
> And even cosmetics aren't a bad reason at all I think.
>
> But I understand that it is annoying that it breaks reporting all the
> time, but would prefer that before licing with not that good column  
> names
> for the next 5 years.... But that are just my 2 cents...
>
> -----Ursprüngliche Nachricht-----
> Von: jbpm-dev-bounces at lists.jboss.org
> [mailto:jbpm-dev-bounces at lists.jboss.org] Im Auftrag von Heiko Braun
> Gesendet: Dienstag, 26. Mai 2009 10:39
> An: jbpm dev
> Betreff: [jbpm-dev] Stabilizing DB schema
>
>
>
> Guys, please be careful with changes to schema. Over the course of the
> last few weeks several
> small changes happend that always break the reporting: Table name
> changes, column name changes, etc.
> At least think twice if the change you do is really necessary it this
> stage or pure cosmetics.
>
> Thanks,
> Heiko
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbpm-dev
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbpm-dev





More information about the jbpm-dev mailing list