cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Gentry <>
Subject Re: CGen includeEntities attribute
Date Thu, 14 Mar 2013 17:52:10 GMT
Hi John,

I recently started using cgen, but didn't look at include (or exclude)
entities because I generate the entire model.  I'm not entirely certain
they are useful in a typical build cycle/environment which builds entities
from scratch.  Is this something you are actively using or just pondering?
 If actively using it, what is your use-case?  Just curious.  Also, I think
a comma-separated list would be fine, too.


On Thu, Mar 14, 2013 at 12:49 PM, John Huss <> wrote:

> I've been using CGen for a bit and one confusing aspect of it to me was the
> way you specific which entities to include for generation.  I expected a
> simple comma-separated list, but it requires a regular expression.  You can
> sort of make it work like a comma-separated list by using something like
> this:
> includeEntities="Customer|Invoice"
> The problem is that if you have entites whose names contain these
> substrings, they will also be included - so an entity named InvoiceDetail
> will also be generated.  You can avoid it by using this:
> includeEntities="Customer|^Invoice$"
> While the vertical bar instead of a comma is unintuitive, but passable,
> requiring this syntax is not friendly.
> So my questions are:
> 1) Are people actually using the reg-ex here for useful, more complex
> things?
> 2) Would it be reasonable to add another mutually-exclusive property that
> just takes a comma-separated list of entity names?
> John

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message