Hi!
Since the last update, DBIx::Class::Schema::Loader automatically creates `view_definition` for views. In case of MySQL it uses `SELECT view_definition FROM information_schema.views ...` query and the result of this query contains the database name along with every table name: `project`.`user` instead of just `user`.
It's a big issue for our project since different users and environments use different database names. It would be great to have view definition without database name or at least disable view_definition generation at all.
Thank you!
From ilmari@ilmari.org on 2017-01-26 18:27:15
:
Hi Vadim,
"Pushtaev Vadim via RT" <bug-DBIx-Class-Schema-Loader@rt.cpan.org>
writes:
> Hi!
>
> Since the last update, DBIx::Class::Schema::Loader automatically
> creates `view_definition` for views. In case of MySQL it uses `SELECT
> view_definition FROM information_schema.views ...` query and the
> result of this query contains the database name along with every table
> name: `project`.`user` instead of just `user`.
Schema::Loader does deliberately not do anything with the view
definition SQL, since that would require a fully-fledged SQL parser.
This is incidentally why it does not introspect the view definition for
DB2, since that only gives you the whole CREATE VIEW statement, not the
body separately.
> It's a big issue for our project since different users and
> environments use different database names. It would be great to have
> view definition without database name or at least disable
> view_definition generation at all.
For non-virtual views, the view definition is only used for ->deploy.
The fact that you're happy with not having it generated at all makes it
seem to me that you're not using deploy, so the definition is purely
informative.
If you really need it, you can add an sqlt_deploy_hook method to the
result class that modifies $view->sql as appropriate for your specific
case.
Hope this helps,
Ilmari
--
"The surreality of the universe tends towards a maximum" -- Skud's Law
"Never formulate a law or axiom that you're not prepared to live with
the consequences of." -- Skud's Meta-Law
From pushtaev@cpan.org on 2017-01-26 20:06:48
:
We do use `deploy` indeed. Previously we just added view_definition manually, but we would be happy to use auto-generated one (we have already monkey-patched Schema::Loader not to generate view_definiton as a workaround).
I understand you don't want to parse SQL, but there is a way to get view definition from MySQL without database name: https://dev.mysql.com/doc/refman/5.7/en/show-create-view.html
On Thu Jan 26 13:27:15 2017, ilmari@ilmari.org wrote:
> Hi Vadim,
>
> "Pushtaev Vadim via RT" <bug-DBIx-Class-Schema-Loader@rt.cpan.org>
> writes:
>
> > Hi!
> >
> > Since the last update, DBIx::Class::Schema::Loader automatically
> > creates `view_definition` for views. In case of MySQL it uses `SELECT
> > view_definition FROM information_schema.views ...` query and the
> > result of this query contains the database name along with every table
> > name: `project`.`user` instead of just `user`.
>
> Schema::Loader does deliberately not do anything with the view
> definition SQL, since that would require a fully-fledged SQL parser.
> This is incidentally why it does not introspect the view definition for
> DB2, since that only gives you the whole CREATE VIEW statement, not the
> body separately.
>
> > It's a big issue for our project since different users and
> > environments use different database names. It would be great to have
> > view definition without database name or at least disable
> > view_definition generation at all.
>
> For non-virtual views, the view definition is only used for ->deploy.
> The fact that you're happy with not having it generated at all makes it
> seem to me that you're not using deploy, so the definition is purely
> informative.
>
> If you really need it, you can add an sqlt_deploy_hook method to the
> result class that modifies $view->sql as appropriate for your specific
> case.
>
> Hope this helps,
>
> Ilmari
>
From ilmari@ilmari.org on 2017-01-27 12:28:53
:
"Pushtaev Vadim via RT" <bug-DBIx-Class-Schema-Loader@rt.cpan.org>
writes:
> We do use `deploy` indeed. Previously we just added view_definition
> manually, but we would be happy to use auto-generated one (we have
> already monkey-patched Schema::Loader not to generate view_definiton
> as a workaround).
> I understand you don't want to parse SQL, but there is a way to get
> view definition from MySQL without database name:
> https://dev.mysql.com/doc/refman/5.7/en/show-create-view.html
That has the same problem as DB2: It includes the whole CREATE VIEW
statement, not just the query. Also, whether it includes the database
name (which is really the schema, in standard SQL parlance) depends on
whether your current schema matches the one of the (tables used) in the
view.
mysql> \r test
mysql> show create view test.bar \G
*************************** 1. row ***************************
View: bar
Create View: CREATE ALGORITHM=UNDEFINED
DEFINER=`ilmari`@`%` SQL SECURITY DEFINER VIEW
`bar` AS select `foo`.`id` AS `id` from `foo`
character_set_client: utf8
collation_connection: utf8_general_ci
1 row in set (0.00 sec)
mysql> \r dbictest
mysql> show create view test.bar \G
*************************** 1. row ***************************
View: bar
Create View: CREATE ALGORITHM=UNDEFINED
DEFINER=`ilmari`@`%` SQL SECURITY DEFINER VIEW
`test`.`bar` AS select `test`.`foo`.`id` AS
`id` from `test`.`foo`
character_set_client: utf8
collation_connection: utf8_general_ci
1 row in set (0.00 sec)
> On Thu Jan 26 13:27:15 2017, ilmari@ilmari.org wrote:
>> Hi Vadim,
>>
>> "Pushtaev Vadim via RT" <bug-DBIx-Class-Schema-Loader@rt.cpan.org>
>> writes:
>>
>> > Hi!
>> >
>> > Since the last update, DBIx::Class::Schema::Loader automatically
>> > creates `view_definition` for views. In case of MySQL it uses `SELECT
>> > view_definition FROM information_schema.views ...` query and the
>> > result of this query contains the database name along with every table
>> > name: `project`.`user` instead of just `user`.
>>
>> Schema::Loader does deliberately not do anything with the view
>> definition SQL, since that would require a fully-fledged SQL parser.
>> This is incidentally why it does not introspect the view definition for
>> DB2, since that only gives you the whole CREATE VIEW statement, not the
>> body separately.
>>
>> > It's a big issue for our project since different users and
>> > environments use different database names. It would be great to have
>> > view definition without database name or at least disable
>> > view_definition generation at all.
>>
>> For non-virtual views, the view definition is only used for ->deploy.
>> The fact that you're happy with not having it generated at all makes it
>> seem to me that you're not using deploy, so the definition is purely
>> informative.
>>
>> If you really need it, you can add an sqlt_deploy_hook method to the
>> result class that modifies $view->sql as appropriate for your specific
>> case.
>>
>> Hope this helps,
>>
>> Ilmari
>>
>
>
>
>
--
"The surreality of the universe tends towards a maximum" -- Skud's Law
"Never formulate a law or axiom that you're not prepared to live with
the consequences of." -- Skud's Meta-Law
Migrated from rt.cpan.org#119996 (status was 'open')
Requestors:
From pushtaev@cpan.org on 2017-01-26 13:26:44 :
From ilmari@ilmari.org on 2017-01-26 18:27:15 :
From pushtaev@cpan.org on 2017-01-26 20:06:48 :
From ilmari@ilmari.org on 2017-01-27 12:28:53 :