Re: how can I figure out what moniker DBIx::Class::Schema::Loader used for a given table?

Hi, the documentation for DBIx::Class::Schema::Loader::Base shows how to control naming for monikers and other elements of your schemas by specifying a version number. If you are not specifiying a version, you are using the default, so consulting the documentation there will show you how the monikers are constructed.

Hope this helps!

The way forward always starts with a minimal test.

Comment on Re: how can I figure out what moniker DBIx::Class::Schema::Loader used for a given table?

Replies are listed 'Best First'.
Re^2: how can I figure out what moniker DBIx::Class::Schema::Loader used for a given table? by tomgracey (Scribe) on Dec 29, 2017 at 02:16 UTC
Thanks for your comment - but I did already look at the docs you mentioned and actually it doesn't help too much. You said "If you are not specifying a version..." - however the user has the option to specify the version. So if I were to try to emulate the module's naming system then I'd need to do it for all versions. Obviously that doesn't make sense. It seems odd to me that the same process that creates the monikers during `make_schema_at` cannot be queried independently of the make process. (This is what I am trying to find a way to do). Thanks for trying to help though...	[reply] [d/l]
Re^3: how can I figure out what moniker DBIx::Class::Schema::Loader used for a given table? by 1nickt (Canon) on Dec 29, 2017 at 03:28 UTC
I guess I can't conceive of any case in which I'd want to give my users that much control over the inner workings of my app. Is it really necessary? If you need to provide access to other options, can you create a wrapper that supports only the ones you want to enable? The way forward always starts with a minimal test.	[reply]