yes I know that and I could do even more.
But anyway is quite not at all readable a reg exp of a sort of more than
100 tables or more than 1000 characters,
it could be too much error prone, like for example a typo error in one
table in the middle of the reg exp
it is quite difficult to spot.
At the same time change and mantain such a long reg exp, instead of use a
YML array structure is not so elegant.
well, I just mean that.

So, it is quite simple to wrapper my request into a reg exp and use the
same chunks of code, but with the gain
that there is a more readable and easily to maintain structure for that
filter.

for example a quick fix right now could be:
use the array declaration for multiple reg exp => the code merge the
string togheter with OR operations.
at least it is more readable have in exact one line one reg exp (in my case
is like one table)
or whatever.

thanks for the replay.




On Mon, Apr 13, 2015 at 1:31 PM, 'Jasper N. Brouwer' via doctrine-user <
[email protected]> wrote:

> I know this doesn’t answer your question directly, but are you aware you
> can mimmic an array with regex?
>
> array(‘table_a’, ‘table_b’) can be written as: /^(?:table_a|table_b)$/
>
> --
> Jasper N. Brouwer
> (@jaspernbrouwer)
>
>
> On 13 April 2015 at 12:48:58, Raffaello Bertini (
> [email protected]) wrote:
> > Based on the article:
> >
> http://docs.doctrine-project.org/projects/doctrine-migrations/en/latest/reference/generating_migrations.html#ignoring-custom-tables
> >
> > at point 5, there is a way to "filter" the current schema with some reg
> exp.
> >
> > I'd like if it is possible to expand this feature with a list (array) of
> > the entities, or as a counterpart have a negative filter wich exclude
> some
> > entities base always with reg exp (useless) and explicit list (array).
> >
> > Otherwise if it still possible to add a "flag" to filter only with the
> > current mapping entities.
> >
> > more precisly in my case:
> > I have a lot of different tables ,
> > as well as temporary table and some schema db not well design at all. (so
> > need migration :))
> > doctrine migration command generate like 3000 lines of code to be dropped
> > and so on without modifing nothing on the actual mapping.
> >
> > the name are a lot different, it is not pratical to filter based on reg
> > exp. You can imagine....
> >
> > It is quite easy to "tell doctrine" to ignore the non mapped entities
> like
> > thay was filtered (negatively in reg exp).
> >
> > Thanks guys if it is possible.
> > I am available to implements the current modifications as well if there
> is
> > no one can do it right now.
> > I think they are good options and expand the use cases for the doctrine2
> > projects. am i right?
> >
> > p.s.:
> > One more thing, even if it is related to symfony2.
> > schema_filter under doctrine.dbal is not valid, it is not recognized as
> > valid option.
> > if someone knows about....
> > (symfony 2.6, the other components as the composer.json file).
> >
> >
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google
> Groups "doctrine-user"
> > group.
> > To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected].
> > To post to this group, send email to [email protected].
> > Visit this group at http://groups.google.com/group/doctrine-user.
> > For more options, visit https://groups.google.com/d/optout.
> >
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "doctrine-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/doctrine-user/Tr4kkpIxwRk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/doctrine-user.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"doctrine-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/doctrine-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to