use namespace::clean -except => 'meta';
-=encoding utf8
-
=head1 NAME
DBIx::Class::Storage::DBI::Replicated - BETA Replicated database support
that the Pool object should get.
my $schema = Schema::Class->clone;
- $schema->storage_type( ['::DBI::Replicated', {balancer=>'::Random'}] );
+ $schema->storage_type(['::DBI::Replicated', { balancer_type => '::Random' }]);
$schema->connection(...);
Next, you need to add in the Replicants. Basically this is an array of
build_datetime_parser
last_insert_id
insert
- insert_bulk
update
delete
dbh
_native_data_type
_get_dbh
sql_maker_class
+ insert_bulk
+ _insert_bulk
_execute
_do_query
- _sth
- _dbh_sth
_dbh_execute
/, Class::MOP::Class->initialize('DBIx::Class::Storage::DBIHacks')->get_method_list ],
reader => [qw/
_arm_global_destructor
_verify_pid
- source_bind_attributes
-
get_use_dbms_capability
set_use_dbms_capability
get_dbms_capability
_dbh_details
_dbh_get_info
+ _determine_connector_driver
+ _extract_driver_from_connect_info
+ _describe_connection
+ _warn_undetermined_driver
+
sql_limit_dialect
sql_quote_char
sql_name_sep
_max_column_bytesize
_is_lob_type
_is_binary_lob_type
+ _is_binary_type
_is_text_lob_type
- sth
+ _prepare_sth
+ _bind_sth_params
/,(
# the capability framework
# not sure if CMOP->initialize does evil things to DBIC::S::DBI, fix if a problem
for my $method (@{$method_dispatch->{unimplemented}}) {
__PACKAGE__->meta->add_method($method, sub {
my $self = shift;
- $self->throw_exception("$method must not be called on ".(blessed $self).' objects');
+ $self->throw_exception("$method() must not be called on ".(blessed $self).' objects');
});
}
=head2 read_handler
-Defines an object that implements the read side of L<BIx::Class::Storage::DBI>.
+Defines an object that implements the read side of L<DBIx::Class::Storage::DBI>.
=cut
=head2 write_handler
-Defines an object that implements the write side of L<BIx::Class::Storage::DBI>,
+Defines an object that implements the write side of L<DBIx::Class::Storage::DBI>,
as well as methods that don't write or read that can be called on only one
storage, methods that return a C<$dbh>, and any methods that don't make sense to
run on a replicant.
around connect_info => sub {
my ($next, $self, $info, @extra) = @_;
+ $self->throw_exception(
+ 'connect_info can not be retrieved from a replicated storage - '
+ . 'accessor must be called on a specific pool instance'
+ ) unless defined $info;
+
my $merge = Hash::Merge->new('LEFT_PRECEDENT');
my %opts;
=head2 around: connect_replicants
All calls to connect_replicants needs to have an existing $schema tacked onto
-top of the args, since L<DBIx::Storage::DBI> needs it, and any C<connect_info>
+top of the args, since L<DBIx::Class::Storage::DBI> needs it, and any
+L<connect_info|DBIx::Class::Storage::DBI/connect_info>
options merged with the master, with replicant opts having higher priority.
=cut
=head2 all_storages
-Returns an array of of all the connected storage backends. The first element
-in the returned array is the master, and the remainings are each of the
+Returns an array of all the connected storage backends. The first element
+in the returned array is the master, and the rest are each of the
replicants.
=cut
Due to the fact that replicants can lag behind a master, you must take care to
make sure you use one of the methods to force read queries to a master should
you need realtime data integrity. For example, if you insert a row, and then
-immediately re-read it from the database (say, by doing $row->discard_changes)
+immediately re-read it from the database (say, by doing
+L<< $result->discard_changes|DBIx::Class::Row/discard_changes >>)
or you insert a row and then immediately build a query that expects that row
to be an item, you should force the master to handle reads. Otherwise, due to
the lag, there is no certainty your data will be in the expected state.
Otherwise, you can force a single query to use the master with the 'force_pool'
attribute:
- my $row = $resultset->search(undef, {force_pool=>'master'})->find($pk);
+ my $result = $resultset->search(undef, {force_pool=>'master'})->find($pk);
-This attribute will safely be ignore by non replicated storages, so you can use
+This attribute will safely be ignored by non replicated storages, so you can use
the same code for both types of systems.
Lastly, you can use the L</execute_reliably> method, which works very much like
## $new_schema will use only the Master storage for all reads/writes while
## the $schema object will use replicated storage.
-=head1 AUTHOR
-
- John Napiorkowski <john.napiorkowski@takkle.com>
-
-Based on code originated by:
+=head1 FURTHER QUESTIONS?
- Norbert Csongrádi <bert@cpan.org>
- Peter Siklósi <einon@einon.hu>
+Check the list of L<additional DBIC resources|DBIx::Class/GETTING HELP/SUPPORT>.
-=head1 LICENSE
+=head1 COPYRIGHT AND LICENSE
-You may distribute this code under the same terms as Perl itself.
+This module is free software L<copyright|DBIx::Class/COPYRIGHT AND LICENSE>
+by the L<DBIx::Class (DBIC) authors|DBIx::Class/AUTHORS>. You can
+redistribute it and/or modify it under the same terms as the
+L<DBIx::Class library|DBIx::Class/COPYRIGHT AND LICENSE>.
=cut
projects / dbsrgits/DBIx-Class.git / blobdiff