Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dbd::sqlite::cookbook(3) [suse man page]

DBD::SQLite::Cookbook(3)				User Contributed Perl Documentation				  DBD::SQLite::Cookbook(3)

NAME
DBD::SQLite::Cookbook - The DBD::SQLite Cookbook DESCRIPTION
This is the DBD::SQLite cookbook. It is intended to provide a place to keep a variety of functions and formals for use in callback APIs in DBD::SQLite. Variance This is a simple aggregate function which returns a variance. It is adapted from an example implementation in pysqlite. package variance; sub new { bless [], shift; } sub step { my ( $self, $value ) = @_; push @$self, $value; } sub finalize { my $self = $_[0]; my $n = @$self; # Variance is NULL unless there is more than one row return undef unless $n || $n == 1; my $mu = 0; foreach my $v ( @$self ) { $mu += $v; } $mu /= $n; my $sigma = 0; foreach my $v ( @$self ) { $sigma += ($x - $mu)**2; } $sigma = $sigma / ($n - 1); return $sigma; } # NOTE: If you use an older DBI (< 1.608), # use $dbh->func(..., "create_aggregate") instead. $dbh->sqlite_create_aggregate( "variance", 1, 'variance' ); The function can then be used as: SELECT group_name, variance(score) FROM results GROUP BY group_name; Variance (Memory Efficient) A more efficient variance function, optimized for memory usage at the expense of precision: package variance2; my $sum = 0; my $count = 0; my %hash; sub new { bless [], shift; } sub step { my ( $self, $value ) = @_; # by truncating and hashing, we can comsume many more data points $value = int($value); # change depending on need for precision # use sprintf for arbitrary fp precision if (defined $hash{$value}) { $hash{$value}++; } else { $hash{$value} = 1; } $sum += $value; $count++; } sub finalize { my $self = $_[0]; # Variance is NULL unless there is more than one row return undef unless $count > 1; # calculate avg my $mu = $sum / $count; my $sigma = 0; foreach my $h (keys %hash) { $sigma += (($h - $mu)**2) * $hash{$h}; } $sigma = $sigma / ($count - 1); return $sigma; } The function can then be used as: SELECT group_name, variance2(score) FROM results GROUP BY group_name; Variance (Highly Scalable) A third variable implementation, designed for arbitrarily large data sets: package variance; my $mu = 0; my $count = 0; my $S = 0 sub new { bless [], shift; } sub step { my ( $self, $value ) = @_; $count++; $delta = $value - $mu; $mu = $mu + $delta/$count $S = $S + $delta*($value - $mu); } sub finalize { my $self = $_[0]; return $S / ($count - 1); } The function can then be used as: SELECT group_name, variance3(score) FROM results GROUP BY group_name; SUPPORT
Bugs should be reported via the CPAN bug tracker at http://rt.cpan.org/NoAuth/ReportBug.html?Queue=DBD-SQLite <http://rt.cpan.org/NoAuth/ReportBug.html?Queue=DBD-SQLite> TO DO
* Add more and varied cookbook recipes, until we have enough to turn them into a seperate CPAN distribution. * Create a series of tests scripts that validate the cookbook recipies. AUTHOR
Adam Kennedy <adamk@cpan.org> COPYRIGHT
Copyright 2009 Adam Kennedy. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of the license can be found in the LICENSE file included with this module. perl v5.12.1 2010-01-08 DBD::SQLite::Cookbook(3)

Check Out this Related Man Page

DBIx::Class::Storage::DBI::SQLite(3)			User Contributed Perl Documentation		      DBIx::Class::Storage::DBI::SQLite(3)

NAME
DBIx::Class::Storage::DBI::SQLite - Automatic primary key class for SQLite SYNOPSIS
# In your table classes use base 'DBIx::Class::Core'; __PACKAGE__->set_primary_key('id'); DESCRIPTION
This class implements autoincrements for SQLite. Known Issues RT79576 NOTE - This section applies to you only if ALL of these are true: * You are or were using DBD::SQLite with a version lesser than 1.38_01 * You are or were using DBIx::Class versions between 0.08191 and 0.08209 (inclusive) or between 0.08240-TRIAL and 0.08242-TRIAL (also inclusive) * You use objects with overloaded stringification and are feeding them to DBIC CRUD methods directly An unfortunate chain of events led to DBIx::Class silently hitting the problem described in RT#79576 <https://rt.cpan.org/Public/Bug/Display.html?id=79576>. In order to trigger the bug condition one needs to supply more than one bind value that is an object with overloaded stringification (numification is not relevant, only stringification is). When this is the case the internal DBIx::Class call to "$sth->bind_param" would be executed in a way that triggers the above-mentioned DBD::SQLite bug. As a result all the logs and tracers will contain the expected values, however SQLite will receive all these bind positions being set to the value of the last supplied stringifiable object. Even if you upgrade DBIx::Class (which works around the bug starting from version 0.08210) you may still have corrupted/incorrect data in your database. DBIx::Class will currently detect when this condition (more than one stringifiable object in one CRUD call) is encountered and will issue a warning pointing to this section. This warning will be removed 2 years from now, around April 2015, You can disable it after you've audited your data by setting the "DBIC_RT79576_NOWARN" environment variable. Note - the warning is emitted only once per callsite per process and only when the condition in question is encountered. Thus it is very unlikely that your logsystem will be flooded as a result of this. METHODS
connect_call_use_foreign_keys Used as: on_connect_call => 'use_foreign_keys' In connect_info to turn on foreign key (including cascading) support for recent versions of SQLite and DBD::SQLite. Executes: PRAGMA foreign_keys = ON See <http://www.sqlite.org/foreignkeys.html> for more information. AUTHOR AND CONTRIBUTORS
See AUTHOR and CONTRIBUTORS in DBIx::Class LICENSE
You may distribute this code under the same terms as Perl itself. perl v5.18.2 2014-01-29 DBIx::Class::Storage::DBI::SQLite(3)
Man Page