1DBIx::Class::Schema::LoUasDdeBerIrx:C::o:MnCatlnrauisabslu::t::eSUdcphgPeremaradl:i:nDLgooFcarudomemerVn:4t:(aM3ta)inounal::UpgradingFromV4(3)
2
3
4

NAME

6       DBIx::Class::Schema::Loader::Manual::UpgradingFromV4 - Important
7       Information Related to Upgrading from Version 0.04006
8

What Changed

10       ·   add_column
11
12           The new Loader detects much more information about columns and sets
13           flags like "is_auto_increment" that it didn't set before.
14
15       ·   RelBuilder
16
17           The new RelBuilder will give you nicer accessor names for
18           relationships, so you will no longer have conflicts between a
19           foreign key column and the relationship accessor itself (if the FK
20           is named "_id".)
21
22           It will also more correctly infer the relationship type, e.g. some
23           relationships that were previously detected as a "has_many" will
24           now be a "might_have" (when it detects a unique constraint on the
25           foreign key column.)
26
27           Also "cascade_delete" and "cascade_copy" are turned off for by
28           default for "has_many" and "might_have" relationships, while
29           "belongs_to" relationships are created with "on_delete =>
30           'CASCADE'" and "on_update => 'CASCADE'" by default. This is
31           overridable via relationship_attrs.
32
33       ·   moniker_map
34
35           Table names are now singularized when determining the "Result"
36           class names. So the table "user_roles" would have become
37           "UserRoles" in 0.04006 but now becomes "UserRole" instead.
38
39       ·   use_namespaces
40
41           Now defaults to on. See "use_namespaces" in
42           DBIx::Class::Schema::Loader::Base and "load_namespaces" in
43           DBIx::Class::Schema.
44
45       ·   Support for more databases
46
47           We now support Microsoft SQL Server and Sybase, and there are also
48           many improvements to the other backends.
49

Backward Compatibility

51       In backward compatibility mode, the Loader will use the old
52       relationship names and types, will not singularize monikers for tables,
53       and "use_namespaces" will be off.
54
55       To control this behavior see "naming" in
56       DBIx::Class::Schema::Loader::Base and "use_namespaces" in
57       DBIx::Class::Schema::Loader::Base.
58
59   Static Schemas
60       When reading a "Schema.pm" from a static schema generated with an 0.04
61       version of Loader, backward compatibility mode will default to on,
62       unless overridden with the "naming" and/or "use_namespaces" attributes.
63
64   Dynamic Schemas
65       Dynamic schemas will always by default use 0.04006 mode and have
66       "use_namespaces" off.
67
68       To upgrade a dynamic schema, set the "naming" and "use_namespaces"
69       attributes (which is proxied to the loader) in your "Schema.pm":
70
71           __PACKAGE__->naming('current');
72           __PACKAGE__->use_namespaces(1);
73

AUTHOR

75       See "AUTHOR" in DBIx::Class::Schema::Loader and "CONTRIBUTORS" in
76       DBIx::Class::Schema::Loader.
77

LICENSE

79       This library is free software; you can redistribute it and/or modify it
80       under the same terms as Perl itself.
81
82
83
84perl v5.12.2           DBIx::Class2:0:1S0c-h0e9m-a0:1:Loader::Manual::UpgradingFromV4(3)
Impressum