1 package DBIx::Class::Journal;
3 use base qw/DBIx::Class/;
8 our $VERSION = '0.900001_02';
10 ## On create/insert, add new entry to AuditLog
14 $self->result_source->schema->_journal_schema;
19 my ($self, @args) = @_;
21 return if($self->in_storage);
23 my $res = $self->next::method(@args);
25 $self->journal_log_insert();
30 sub journal_log_insert
34 if ( $self->in_storage ) {
35 my $j = $self->_journal_schema;
36 my $change_id = $j->journal_create_change()->id;
37 $j->journal_update_or_create_log_entry( $self, create_id => $change_id );
38 $j->journal_record_in_history( $self, audit_change_id => $change_id );
42 ## On delete, update delete_id of AuditLog
46 my ($self, @rest) = @_;
47 $self->next::method(@rest);
48 $self->journal_log_delete(@rest);
51 sub journal_log_delete
55 unless ($self->in_storage) {
56 my $j = $self->_journal_schema;
57 $j->journal_update_or_create_log_entry( $self, delete_id => $j->journal_create_change->id );
61 ## On update, copy previous row's contents to AuditHistory
65 my ($self, $upd, @rest) = @_;
66 $self->journal_log_update($upd, @rest);
67 $self->next::method($upd, @rest);
70 sub journal_log_update
72 my ($self, $upd, @rest) = @_;
76 my $j = $self->_journal_schema;
78 my $change = $j->journal_create_change;
79 my $prev = $self->result_source->resultset->find( $self->ident_condition );
80 $j->journal_record_in_history( $prev, audit_change_id => $change );
86 DBIx::Class::Journal - auditing for tables managed by DBIx::Class
91 use base 'DBIx::Class::Schema';
93 __PACKAGE__->load_components(qw/+DBIx::Class::Schema::Journal/);
95 __PACKAGE__->journal_connection(['dbi:SQLite:t/var/Audit.db']);
96 __PACKAGE__->journal_user(['My::Schema::User', {'foreign.userid' => 'self.user_id'}]);
101 $schema->changeset_user($user->id);
102 my $new_artist = $schema->txn_do( sub {
103 return = $schema->resultset('Artist')->create({ name => 'Fred' });
109 The purpose of this L<DBIx::Class> component module is to create an
110 audit-trail for all changes made to the data in your database (via a
111 DBIx::Class schema). It creates changesets and assigns each
112 create/update/delete operation an id. The creation and deletion date
113 of each row is stored, as well as the previous contents of any row
116 All queries which want auditing should be called using
117 L<DBIx::Class::Schema/txn_do>, which is used to create changesets for
120 To track who did which changes, the user_id (an integer) of the
121 current user can be set, a session_id can also be set, both are
124 To access the auditing schema to look at the auditdata or revert a
125 change, use C<< $schema->_journal_schema >>.
129 The journal schema contains a number of tables.
135 Each changeset row has an auto-incremented ID, optional user_id and
136 session_id, and a set_date which defaults to the current datetime.
138 A ChangeSet has_many Changes.
142 Each change/operation done in the transaction is recorded as a row in
143 the ChangeLog table. It contains an auto-incrementing ID, the
144 changeset_id and an order column for the ordering of each change in
149 For every table in the original database that is to be audited, an
150 AuditLog table is created. Each auditlog row has an id which will
151 contain the primary key of the table it is associated with. (NB:
152 currently only supports integer-based single column PKs). The
153 create_id and delete_id fields contain the IDs of the Changes that
154 created or deleted this row.
158 For every table in the original database to be audited, an
159 AuditHistory table is created. Each row has a change_id field
160 containing the ID of the ChangeLog row. The other fields correspond to
161 all the fields from the original table. Each time a column value in
162 the original table is changed, the entire row contents before the
163 change are added as a new row in this table.
171 =item journal_connection \@connect_info
173 Set the connection information for the database to save your audit
176 Leaving this blank assumes you want to store the audit data into your current
177 database. The storage object will be shared by the regular schema and the
180 =item journal_sources \@source_names
182 Set a list of source names you would like to audit, if unset, all
185 NOTE: Currently only sources with a single-column PK are supported, so
186 use this method if you have sources with multi-column PKs.
188 =item journal_storage_type $type
190 Enter the special storage type of your journal schema if needed. See
191 L<DBIx::Class::Storage::DBI> for more information on storage types.
193 =item journal_user \@rel
195 The user_id column in the L</ChangeSet> will be linked to your user id
196 with a belongs_to relation, if this is set with the appropriate
199 =item journal_deploy_on_connect $bool
201 If set to a true value will cause C<journal_schema_deploy> to be called on
204 Not reccomended, but present for backwards compatibility.
206 =item changeset_user $user_id
208 Set the user_id for the following changeset(s). This must be an integer.
210 =item changeset_session $session_id
212 Set the session_id for the following changeset(s). This must be an integer.
214 =item txn_do $code_ref, @args
216 Overloaded L<DBIx::Class::Schema/txn_do>, this must be used to start a
217 new changeset to cover a group of changes. Each subsequent change to
218 an audited table will use the changeset_id created in the most recent
221 Currently nested C<txn_do> calls cause a single ChangeSet object to be created.
227 L<DBIx::Class> - You'll need it to use this.
231 Only single-column integer primary key'd tables are supported for auditing so far.
233 Updates made via L<DBIx::Class::ResultSet/update> are not yet supported.
235 No API for viewing or restoring changes yet.
237 Patches for the above welcome ;)
241 Jess Robinson <castaway@desert-island.me.uk>
243 Matt S. Trout <mst@shadowcatsystems.co.uk> (ideas and prodding)
247 You may distribute this code under the same terms as Perl itself.