DBIx::Class::Schema::Loader::Base - Base DBIx::Class::Schema::Loader Implementation.
See DBIx::Class::Schema::Loader
This is the base class for the storage-specific DBIx::Class::Schema::* classes,
and implements the common functionality between them.
These constructor options are the base options for "loader_options" in DBIx::Class::Schema::Loader. Available constructor options are:
Skip setting up relationships. The default is to attempt the loading of relationships.
Skip loading of other classes in @INC. The default is to merge all other classes with the same name found in @INC into the schema file we are creating.
Static schemas (ones dumped to disk) will, by default, use the new-style relationship names and singularized Results, unless you're overwriting an existing dump made by an older version of DBIx::Class::Schema::Loader, in which case the backward compatible RelBuilder will be activated, and the appropriate monikerization used.
Specifying
naming => 'current'
will disable the backward-compatible RelBuilder and use the new-style relationship names along with singularized Results, even when overwriting a dump made with an earlier version.
The option also takes a hashref:
naming => { relationships => 'v7', monikers => 'v7' }
The keys are:
How to name relationship accessors.
How to name Result classes.
How to name column accessors in Result classes.
The values can be:
Latest style, whatever that happens to be.
Unsingularlized monikers, has_many only relationships with no _id stripping.
Monikers singularized as whole words, might_have relationships for FKs on UNIQUE constraints, _id stripping for belongs_to relationships.
Some of the _id stripping edge cases in 0.05003 have been reverted for the v5 RelBuilder.
All monikers and relationships are inflected using Lingua::EN::Inflect::Phrase, and there is more aggressive _id stripping from relationship names.
In general, there is very little difference between v5 and v6 schemas.
This mode is identical to v6 mode, except that monikerization of CamelCase table names is also done correctly.
CamelCase column names in case-preserving mode will also be handled correctly for relationship name inflection. See "preserve_case".
In this mode, CamelCase "column_accessors" are normalized based on case transition instead of just being lowercased, so FooId becomes foo_id.
If you don't have any CamelCase table or column names, you can upgrade without breaking any of your code.
Dynamic schemas will always default to the 0.04XXX relationship names and won't singularize Results for backward compatibility, to activate the new RelBuilder and singularization put this in your Schema.pm file:
__PACKAGE__->naming('current');
Or if you prefer to use 0.05XXX features but insure that nothing breaks in the next major version upgrade:
__PACKAGE__->naming('v5');
By default POD will be generated for columns and relationships, using database metadata for the text if available and supported.
Reading database metadata (e.g. COMMENT ON TABLE some_table ...) is only supported for Postgres right now.
Set this to 0 to turn off all POD generation.
Controls where table comments appear in the generated POD. Smaller table comments are appended to the NAME section of the documentation, and larger ones are inserted into DESCRIPTION instead. You can force a DESCRIPTION section to be generated with the comment always, only use NAME, or choose the length threshold at which the comment is forced into the description.
Use NAME section only.
Force DESCRIPTION always.
Use DESCRIPTION if length > "pod_comment_spillover_length", this is the default.
When pod_comment_mode is set to auto, this is the length of the comment at which it will be forced into a separate description section.
The default is 60
Hashref of attributes to pass to each generated relationship, listed by type. Also supports relationship type 'all', containing options to pass to all generated relationships. Attributes set for more specific relationship types override those set in 'all'.
For example:
relationship_attrs => {
belongs_to => { is_deferrable => 1 },
},
use this to make your foreign key constraints DEFERRABLE.
If set to true, each constructive DBIx::Class statement the loader decides to execute will be warn-ed before execution.
Set the name of the schema to load (schema in the sense that your database vendor means it). Does not currently support loading more than one schema name.
Only load tables matching regex. Best specified as a qr// regex.
Exclude tables matching regex. Best specified as a qr// regex.
Overrides the default table name to moniker translation. Can be either a hashref of table keys and moniker values, or a coderef for a translator function taking a single scalar table name argument and returning a scalar moniker. If the hash entry does not exist, or the function returns a false value, the code falls back to default behavior for that table name.
The default behavior is to split on case transition and non-alphanumeric boundaries, singularize the resulting phrase, then join the titlecased words together. Examples:
Table Name | Moniker Name
---------------------------------
luser | Luser
luser_group | LuserGroup
luser-opts | LuserOpt
stations_visited | StationVisited
routeChange | RouteChange
Just like "moniker_map" above (can be hash/code-ref, falls back to default if hash key does not exist or coderef returns false), but acts as a map for pluralizing relationship names. The default behavior is to utilize "to_PL" in Lingua::EN::Inflect::Number.
As "inflect_plural" above, but for singularizing relationship names. Default behavior is to utilize "to_S" in Lingua::EN::Inflect::Number.
Base class for your schema classes. Defaults to 'DBIx::Class::Schema'.
Base class for your table classes (aka result classes). Defaults to 'DBIx::Class::Core'.
List of additional base classes all of your table classes will use.
List of additional base classes all of your table classes will use that need to be leftmost.
List of additional classes which all of your table classes will use.
List of additional components to be loaded into all of your table classes. A good example would be InflateColumn::DateTime
List of additional ResultSet components to be loaded into your table classes. A good example would be AlwaysRS. Component ResultSetManager will be automatically added to the above components list if this option is set.
This is now the default, to go back to "load_classes" in DBIx::Class::Schema pass a 0.
Generate result class names suitable for "load_namespaces" in DBIx::Class::Schema and call that instead of "load_classes" in DBIx::Class::Schema. When using this option you can also specify any of the options for load_namespaces (i.e. result_namespace, resultset_namespace, default_resultset_class), and they will be added to the call (and the generated result class names adjusted appropriately).
This option is designed to be a tool to help you transition from this loader to a manually-defined schema when you decide it's time to do so.
The value of this option is a perl libdir pathname. Within that directory this module will create a baseline manual DBIx::Class::Schema module set, based on what it creates at runtime in memory.
The created schema class will have the same classname as the one on which you are setting this option (and the ResultSource classes will be based on this name as well).
Normally you wouldn't hard-code this setting in your schema class, as it is meant for one-time manual usage.
See "dump_to_dir" in DBIx::Class::Schema::Loader for examples of the recommended way to access this functionality.
Deprecated. See "really_erase_my_files" below, which does *not* mean the same thing as the old dump_overwrite setting from previous releases.
Default false. If true, Loader will unconditionally delete any existing files before creating the new ones from scratch when dumping a schema to disk.
The default behavior is instead to only replace the top portion of the file, up to and including the final stanza which contains # DO NOT MODIFY THIS OR ANYTHING ABOVE! leaving any customizations you placed after that as they were.
When really_erase_my_files is not set, if the output file already exists, but the aforementioned final stanza is not found, or the checksum contained there does not match the generated contents, Loader will croak and not touch the file.
You should really be using version control on your schema classes (and all of the rest of your code for that matter). Don't blame me if a bug in this code wipes something out when it shouldn't have, you've been warned.
Default false. If false, when updating existing files, Loader will refuse to modify any Loader-generated code that has been modified since its last run (as determined by the checksum Loader put in its comment lines).
If true, Loader will discard any manual modifications that have been made to Loader-generated code.
Again, you should be using version control on your schema classes. Be careful with this option.
Hook for adding extra attributes to the column_info for a column.
Must be a coderef that returns a hashref with the extra attributes.
Receives the table name, column name and column_info.
For example:
custom_column_info => sub {
my ($table_name, $column_name, $column_info) = @_;
if ($column_name eq 'dog' && $column_info->{default_value} eq 'snoopy') {
return { is_snoopy => 1 };
}
},
This attribute can also be used to set inflate_datetime on a non-datetime column so it also receives the "datetime_timezone" and/or "datetime_locale".
Sets the timezone attribute for DBIx::Class::InflateColumn::DateTime for all columns with the DATE/DATETIME/TIMESTAMP data_types.
Sets the locale attribute for DBIx::Class::InflateColumn::DateTime for all columns with the DATE/DATETIME/TIMESTAMP data_types.
File in Perl format, which should return a HASH reference, from which to read loader options.
Usually column names are lowercased, to make them easier to work with in DBIx::Class. This option lets you turn this behavior off, if the driver supports it.
Drivers for case sensitive databases like Sybase ASE or MSSQL with a case-sensitive collation will turn this option on unconditionally.
Currently the drivers for SQLite, mysql, MSSQL and Firebird/InterBase support setting this option.
Set to true to prepend the "db_schema" to table names for __PACKAGE__->table calls, and to some other things like Oracle sequences.
None of these methods are intended for direct invocation by regular users of DBIx::Class::Schema::Loader. Some are proxied via DBIx::Class::Schema::Loader.
Constructor for DBIx::Class::Schema::Loader::Base, used internally by DBIx::Class::Schema::Loader.
Does the actual schema-construction work.
Arguments: schema
Rescan the database for changes. Returns a list of the newly added table monikers.
The schema argument should be the schema class or object to be affected. It should probably be derived from the original schema_class used during "load".
Returns a sorted list of loaded tables, using the original database table names.
Returns a hashref of loaded table to moniker mappings. There will be two entries for each table, the original name and the "normalized" name, in the case that the two are different (such as databases that like uppercase table names, or preserve your original mixed-case definitions, or what-have-you).
Returns a hashref of table to class mappings. In some cases it will contain multiple entries per table for the original and normalized table names, as above in "monikers".
See "AUTHOR" in DBIx::Class::Schema::Loader and "CONTRIBUTORS" in DBIx::Class::Schema::Loader.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
