05-21-2008
Awesome! Works
Thanks scarfake
That's how we roll!
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i'm on freebsd 5.2.1, and from a fresh installation i've used pkg_add for the latest ported version of apache, as well as installing php 5. supposedly php5 comes with native support for sqlite (in the binary package), and this is what i added.
i am trying to install a site engine (the 'gyrator'... (0 Replies)
Discussion started by: brandan
0 Replies
2. HP-UX
Hi everybody,
We have a cgi application which accesses sqlite database. It works fine in Linux environment but the same code doesn't enter data into the database when done in HP-UX environment. Should the codes vary depending on whether it is Linux or HP-UX.
Regards
Ruma (1 Reply)
Discussion started by: perlprg
1 Replies
3. Shell Programming and Scripting
Hello All,
I am trying to write a Perl script that is using 'SQLite' as the application needs a very light weight Database. I wanted to know how to catch exceptions when I run queries in SQLite. Without this the Perl script comes to a halt everytime an exception occurs. Please help.
Regards,... (4 Replies)
Discussion started by: garric
4 Replies
4. Linux
Hi guys,
Can we use squid_db_auth to authenticate squid users against SQLite database? I googled but all configurations are in MySQL. (0 Replies)
Discussion started by: majid.merkava
0 Replies
5. Shell Programming and Scripting
hlow all
i have file like this :
BDG0100.2011091620162100CF5341.DAT
BDG0100.2011091720175500CF5342.DAT
BDG0100.2011091820192900CF5343.DAT
BDG0100.2011091920210600CF5344.DAT
but now i want make file like this
20110916.DAT
20110919.DAT
20110918.DAT
20110919.DAT
so what i can do that... (3 Replies)
Discussion started by: zvtral
3 Replies
6. UNIX and Linux Applications
Hello,
I'm not sure this is quite the right place, but there do seem to be allot of posts with folks using ruby to play nicely with databases so I thought I would give it a go.
I am starting a long process of developing a database application bases on SQLite and ruby. This will run on various... (1 Reply)
Discussion started by: LMHmedchem
1 Replies
7. Shell Programming and Scripting
Okay, so this one is a bit above my knowledge level so I'm hoping for some pointers.
Here's the scenario:
I have a backup system on my network that makes single file images of the machines it's backing up and uses an sqlite database to keep track of everything. As is pretty typical with... (2 Replies)
Discussion started by: NyxPDX
2 Replies
8. UNIX for Beginners Questions & Answers
Hi there,
I have multiple rows of data.
For example:
S/N | Name| Age
I would like to store them into sqlite database after doing some grepping in CSV and output them into console/html format.
Will it be possible? (1 Reply)
Discussion started by: alvinoo
1 Replies
LEARN ABOUT CENTOS
test::synopsis
Test::Synopsis(3) User Contributed Perl Documentation Test::Synopsis(3)
NAME
Test::Synopsis - Test your SYNOPSIS code
SYNOPSIS
# xt/synopsis.t (with Module::Install::AuthorTests)
use Test::Synopsis;
all_synopsis_ok();
# Or, run safe without Test::Synopsis
use Test::More;
eval "use Test::Synopsis";
plan skip_all => "Test::Synopsis required for testing" if $@;
all_synopsis_ok();
DESCRIPTION
Test::Synopsis is an (author) test module to find .pm or .pod files under your lib directory and then make sure the example snippet code in
your SYNOPSIS section passes the perl compile check.
Note that this module only checks the perl syntax (by wrapping the code with "sub") and doesn't actually run the code.
Suppose you have the following POD in your module.
=head1 NAME
Awesome::Template - My awesome template
=head1 SYNOPSIS
use Awesome::Template;
my $template = Awesome::Template->new;
$tempalte->render("template.at");
=head1 DESCRIPTION
An user of your module would try copy-paste this synopsis code and find that this code doesn't compile because there's a typo in your
variable name $tempalte. Test::Synopsis will catch that error before you ship it.
VARIABLE DECLARATIONS
Sometimes you might want to put some undeclared variables in your synopsis, like:
=head1 SYNOPSIS
use Data::Dumper::Names;
print Dumper($scalar, @array, \%hash);
This assumes these variables like $scalar are defined elsewhere in module user's code, but Test::Synopsis, by default, will complain that
these variables are not declared:
Global symbol "$scalar" requires explicit package name at ...
In this case, you can add the following POD sequence elsewhere in your POD:
=for test_synopsis
no strict 'vars'
Or more explicitly,
=for test_synopsis
my($scalar, @array, %hash);
Test::Synopsis will find these "=for" blocks and these statements are prepended before your SYNOPSIS code when being evaluated, so those
variable name errors will go away, without adding unnecessary bits in SYNOPSIS which might confuse users.
AUTHOR
Tatsuhiko Miyagawa <miyagawa@bulknews.net>
Goro Fuji blogged about the original idea at <http://d.hatena.ne.jp/gfx/20090224/1235449381> based on the testing code taken from
Test::Weaken.
LICENSE
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
SEE ALSO
Test::Pod, Test::UseAllModules, Test::Inline, Test::Snippet
perl v5.16.3 2009-07-06 Test::Synopsis(3)