[29967] in Perl-Users-Digest
Perl-Users Digest, Issue: 1210 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Jan 18 06:09:38 2008
Date: Fri, 18 Jan 2008 03:09:05 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 18 Jan 2008 Volume: 11 Number: 1210
Today's topics:
Filtering two files with uncommon column <madhurrajn@gmail.com>
Re: In perl 5.10, is $needle ~~ @haystack binary search <g_m@remove-comcast.net>
Making variable field names <ldolan@thinkinghatbigpond.net.au>
Re: Making variable field names <usenet@davidfilmer.com>
Module build time <justin.0801@purestblue.com>
Re: Module build time <justin.0801@purestblue.com>
new CPAN modules on Fri Jan 18 2008 (Randal Schwartz)
non nntp usenet <invalid@invalid.net>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Problem directing BCP Error to Error file <rajpreetsidhu@gmail.com>
Re: To update one file with the another file's data.. clearguy02@yahoo.com
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 18 Jan 2008 01:26:33 -0800 (PST)
From: Madhur <madhurrajn@gmail.com>
Subject: Filtering two files with uncommon column
Message-Id: <a1146611-2990-482c-aa7b-1429294b2c99@l32g2000hse.googlegroups.com>
I would like to know the best way of generating filter of two files
based upon the following condition
I have two files. Contents of the first file is
File 1
abc def hij
asd sss lmn
hig pqr mno
File 2
jih def asd
poi iuu wer
wer pqr jjj
I would like have the output as
Output
File1
asd sss lmn
File2
poi iuu wer
Basically I want to compare the two files based on second column. If
the second
column matches on both the files do not print anything, else if there
is no matc
h in for the second column for first file in second file then print it
under Fil
e1 header, else if there is no match for the second column for second
file in fi
rst file print it under File2 header.
Thankyou
Madhur
------------------------------
Date: Fri, 18 Jan 2008 03:24:33 -0500
From: "~greg" <g_m@remove-comcast.net>
Subject: Re: In perl 5.10, is $needle ~~ @haystack binary search?
Message-Id: <YPqdnfL8m6i2_Q3anZ2dnUVZ_hGdnZ2d@comcast.com>
"Jim Cochrane" >
>
> By the way, does anyone know how to search for something like
> perl ~~
> on google? I've not been able to figure out a way. (Perhaps it's not
> possible.)
>
Nothing is ever impossible.
It just sometimes takes too long
(eg > expected remaining duration of the universe.)
this
http://www.krugle.org/
may not help very often.
But it's promising, and fun.
~greg
------------------------------
Date: Fri, 18 Jan 2008 04:09:07 GMT
From: "Peter Jamieson" <ldolan@thinkinghatbigpond.net.au>
Subject: Making variable field names
Message-Id: <DDVjj.4669$421.1047@news-server.bigpond.net.au>
I have many tables of results, a sample record looks like as below
in my code together with fields in the db.
The problem is this. Not every table I receive has the same fields.
Sometimes there are fields, "test4", "test5" for example.There is always
a fixed number of 7 fields.
Is it possible to have my code change the INSERT INTO statement so that the
fields change
depending on the fields in each table?....of course the db will have all
possible fields
included.
In other words, can the field names be variables?...if so what is the syntax
for this?
Any help appreciated!
#!/usr/bin/perl -w
use strict;
use warnings;
use Win32::ODBC;
use dbi;
my $mdb = "Treatment.mdb";
my $dns = "driver=Microsoft Access Driver (*.mdb);dbq=$mdb";
# Connect to the mdb and prepare request
my $dbh = DBI->connect("dbi:ODBC:$dns", ',') or die "Connection to $mdb
failed!\n";
# sample results
$mdate = '17/1/2008'; $venue = 'ICPM'; $patient = 'G Gomez'; $dob =
'21/08/1977'; $test1 = 88.5;
$test2 = 75.1; $test3 = 81.9;
# Load the results into the database
my $input = $dbh->prepare("INSERT INTO
Treatment_table(mdate,venue,patient,dob,test1,test2,test3)
VALUES (?,?,?,?,?,?,?)");
$input->execute( $mdate, $venue, $patient, $dob, $test1, $test2, $test3);
$dbh->disconnect();
------------------------------
Date: Thu, 17 Jan 2008 23:18:52 -0800
From: David Filmer <usenet@davidfilmer.com>
Subject: Re: Making variable field names
Message-Id: <DP-dnZAC9_cBzw3a4p2dnAA@giganews.com>
Peter Jamieson wrote:
> Is it possible to have my code change the INSERT INTO statement so that the
> fields change depending on the fields in each table?
The SQL command is just a string scalar. You can interpolate variables
in it just like any other string, such as:
my $sth = $dbh->prepare("INSERT INTO
Treatment_table(mdate,venue,patient,dob,$c1,$c2,$c3)...
If you want to determine what the column names are for a particular
table, use the column_info method of DBI.
Of course, if you change either the table or the column names, you must
build a separate prepare statement. You cannot prepare a generic
database plan and then execute it against different tables and columns.
------------------------------
Date: Fri, 18 Jan 2008 08:47:04 -0000
From: Justin C <justin.0801@purestblue.com>
Subject: Module build time
Message-Id: <36f9.47906788.ed065@zem>
I'm installing, from cpan, with "cpan -i", Math::TrulyRandom. It's now
been building for about 18 hours (I went home and left it over-night).
One of my CPUs is at 100% (well, it's core2duo), at least I've got the
other one with which I can carry on working!
The package is only, IIRC, 4.2Kb. Would you agree that there is a
problem, or should I let it run over the weekend if it's still going
when I finish work today?
Thank you for your suggestions.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Fri, 18 Jan 2008 10:08:38 -0000
From: Justin C <justin.0801@purestblue.com>
Subject: Re: Module build time
Message-Id: <461f.47907aa6.14573@zem>
On 2008-01-18, Justin C <justin.0801@purestblue.com> wrote:
> I'm installing, from cpan, with "cpan -i", Math::TrulyRandom. It's now
> been building for about 18 hours (I went home and left it over-night).
> One of my CPUs is at 100% (well, it's core2duo), at least I've got the
> other one with which I can carry on working!
>
> The package is only, IIRC, 4.2Kb. Would you agree that there is a
> problem, or should I let it run over the weekend if it's still going
> when I finish work today?
Bad form following up myself. It's stopped at the testing stage. I've
looked at the test.pl in the build directory and, it's quite a small
script - very small, about ten lines. I don't think it's generating any
random numbers, and that's why it's failing to test.
I've force-installed it, and shall give it a bit of a test myself and
report a bug if necessary.
Justin.
--
Justin C, by the sea.
------------------------------
Date: Fri, 18 Jan 2008 05:42:21 GMT
From: merlyn@stonehenge.com (Randal Schwartz)
Subject: new CPAN modules on Fri Jan 18 2008
Message-Id: <JutruL.1o8r@zorch.sf-bay.org>
The following modules have recently been added to or updated in the
Comprehensive Perl Archive Network (CPAN). You can install them using the
instructions in the 'perlmodinstall' page included with your Perl
distribution.
Apache2-ASP-1.24
http://search.cpan.org/~johnd/Apache2-ASP-1.24/
Perl extension for ASP on mod_perl2.
----
App-Env-0.05
http://search.cpan.org/~djerius/App-Env-0.05/
manage application specific environments
----
App-Music-PlayTab-2.018
http://search.cpan.org/~jv/App-Music-PlayTab-2.018/
Print chords of songs in a tabular fashion.
----
BerkeleyDB-0.33
http://search.cpan.org/~pmqs/BerkeleyDB-0.33/
Perl extension for Berkeley DB version 2, 3 or 4
----
Catalyst-Controller-Atompub-0.3.2
http://search.cpan.org/~takeru/Catalyst-Controller-Atompub-0.3.2/
A Catalyst controller for the Atom Publishing Protocol
----
Catalyst-Model-Estraier-0.0.5
http://search.cpan.org/~takeru/Catalyst-Model-Estraier-0.0.5/
Hyper Estraier model class for Catalyst
----
Class-DBI-Plugin-DeepAbstractSearch-0.06
http://search.cpan.org/~sriha/Class-DBI-Plugin-DeepAbstractSearch-0.06/
deep_search_where() for Class::DBI
----
Class-DBI-Plugin-DeepAbstractSearch-0.07
http://search.cpan.org/~sriha/Class-DBI-Plugin-DeepAbstractSearch-0.07/
deep_search_where() for Class::DBI
----
Class-DBI-Plugin-DeepAbstractSearch-0.08
http://search.cpan.org/~sriha/Class-DBI-Plugin-DeepAbstractSearch-0.08/
deep_search_where() for Class::DBI
----
DBD-Pg-2.0.0_1
http://search.cpan.org/~dbdpg/DBD-Pg-2.0.0_1/
PostgreSQL database driver for the DBI module
----
DBD-Pg-2.0.0_2
http://search.cpan.org/~dbdpg/DBD-Pg-2.0.0_2/
PostgreSQL database driver for the DBI module
----
DBIx-InterpolationBinding-0.05
http://search.cpan.org/~lukeross/DBIx-InterpolationBinding-0.05/
Perl extension for turning perl double-quote string interpolation into DBI bind parameters.
----
DBIx-StORM-0.05
http://search.cpan.org/~lukeross/DBIx-StORM-0.05/
Perl extension for object-relational mapping
----
DBIx-Transaction-1.000
http://search.cpan.org/~crakrjack/DBIx-Transaction-1.000/
Allow transactions to be nested in DBI
----
DBIx-Transaction-1.001
http://search.cpan.org/~crakrjack/DBIx-Transaction-1.001/
Allow transactions to be nested in DBI
----
Data-Thunk-0.02
http://search.cpan.org/~nuffin/Data-Thunk-0.02/
A sneakier Scalar::Defer ;-)
----
Data-Thunk-0.03
http://search.cpan.org/~nuffin/Data-Thunk-0.03/
A sneakier Scalar::Defer ;-)
----
Encode-JP-Mobile-0.18
http://search.cpan.org/~miyagawa/Encode-JP-Mobile-0.18/
????????? Shift_JIS (CP932) / UTF-8 ????????
----
Encode-JP-Mobile-0.19
http://search.cpan.org/~miyagawa/Encode-JP-Mobile-0.19/
????????? Shift_JIS (CP932) / UTF-8 ????????
----
Encode-JP-Mobile-0.20
http://search.cpan.org/~miyagawa/Encode-JP-Mobile-0.20/
????????? Shift_JIS (CP932) / UTF-8 ????????
----
Encode-JP-Mobile-0.21
http://search.cpan.org/~miyagawa/Encode-JP-Mobile-0.21/
????????? Shift_JIS (CP932) / UTF-8 ????????
----
Gtk2-Ex-TickerView-1
http://search.cpan.org/~kryde/Gtk2-Ex-TickerView-1/
scrolling ticker display widget
----
HTML-Tested-ClassDBI-0.15
http://search.cpan.org/~bosu/HTML-Tested-ClassDBI-0.15/
Enhances HTML::Tested to work with Class::DBI
----
Keystone-Resolver-1.12
http://search.cpan.org/~mirk/Keystone-Resolver-1.12/
an OpenURL resolver
----
Language-Befunge-Vector-XS-0.2.1
http://search.cpan.org/~jquelin/Language-Befunge-Vector-XS-0.2.1/
Language::Befunge::Vector rewritten for speed
----
Language-Befunge-Vector-XS-0.2.2
http://search.cpan.org/~jquelin/Language-Befunge-Vector-XS-0.2.2/
Language::Befunge::Vector rewritten for speed
----
List-Rotation-Cycle-1.006
http://search.cpan.org/~pelagic/List-Rotation-Cycle-1.006/
Cycle through a list of values via a singleton object implemented as closure.
----
Math-Wavelet-Haar-0.05
http://search.cpan.org/~simcop/Math-Wavelet-Haar-0.05/
Perl extension for transforming data with the Haar Wavelet
----
Memcached-libmemcached-0.1306
http://search.cpan.org/~timb/Memcached-libmemcached-0.1306/
Thin fast full interface to the libmemcached client API
----
MooseX-Async-0.03
http://search.cpan.org/~perigrin/MooseX-Async-0.03/
The Orphanange of Asynchronous Love Children
----
MooseX-POE-0.04
http://search.cpan.org/~perigrin/MooseX-POE-0.04/
The Illicit Love Child of Moose and POE
----
Net-MirrorDir-0.07
http://search.cpan.org/~knorr/Net-MirrorDir-0.07/
Perl extension for compare local-directories and remote-directories with each other
----
PDF-API2-0.69
http://search.cpan.org/~areibens/PDF-API2-0.69/
A Perl Module Chain to faciliate the Creation and Modification of High-Quality "Portable Document Format (aka. PDF)" Files.
----
POE-Component-Client-Ident-1.08
http://search.cpan.org/~bingos/POE-Component-Client-Ident-1.08/
A component that provides non-blocking ident lookups to your sessions.
----
POE-Component-Server-Chargen-1.08
http://search.cpan.org/~bingos/POE-Component-Server-Chargen-1.08/
A POE component that implements an RFC 864 Chargen server.
----
POE-Component-Server-Echo-1.58
http://search.cpan.org/~bingos/POE-Component-Server-Echo-1.58/
A POE component that implements an RFC 862 Echo server.
----
POE-Component-Server-SimpleHTTP-1.38
http://search.cpan.org/~bingos/POE-Component-Server-SimpleHTTP-1.38/
Perl extension to serve HTTP requests in POE.
----
POE-Component-Server-SimpleHTTP-1.40
http://search.cpan.org/~bingos/POE-Component-Server-SimpleHTTP-1.40/
Perl extension to serve HTTP requests in POE.
----
POE-Loop-EV-0.04
http://search.cpan.org/~agrundma/POE-Loop-EV-0.04/
a bridge that supports EV from POE
----
Parley-0.58_13
http://search.cpan.org/~chisel/Parley-0.58_13/
Message board / forum application
----
Parse-Eyapp-1.106
http://search.cpan.org/~casiano/Parse-Eyapp-1.106/
Extensions for Parse::Yapp
----
Parse-Flash-Cookie-0.04
http://search.cpan.org/~aff/Parse-Flash-Cookie-0.04/
A flash cookie parser.
----
Parse-Flash-Cookie-0.05
http://search.cpan.org/~aff/Parse-Flash-Cookie-0.05/
A flash cookie parser.
----
Parse-Marpa-0.202000
http://search.cpan.org/~jkegl/Parse-Marpa-0.202000/
(Alpha) Earley's algorithm with LR(0) precomputation
----
Pod-Extract-URI-0.1
http://search.cpan.org/~imalpass/Pod-Extract-URI-0.1/
Extract URIs from POD
----
SVN-Class-0.06
http://search.cpan.org/~karman/SVN-Class-0.06/
manipulate Subversion workspaces with Perl objects
----
SelfLoader-1.15
http://search.cpan.org/~smueller/SelfLoader-1.15/
load functions only on demand
----
Sledge-SessionManager-Auto-0.02
http://search.cpan.org/~mikihoshi/Sledge-SessionManager-Auto-0.02/
Sledge's session manger switcher
----
Sledge-SessionManager-MobileID-0.01
http://search.cpan.org/~mikihoshi/Sledge-SessionManager-MobileID-0.01/
Sledge's session manager use mobile phone identify.
----
Spreadsheet-Engine-0.11
http://search.cpan.org/~tmtm/Spreadsheet-Engine-0.11/
Core calculation engine for a spreadsheet
----
Spreadsheet-WriteExcel-Worksheet-SheetProtection-0.02
http://search.cpan.org/~sriha/Spreadsheet-WriteExcel-Worksheet-SheetProtection-0.02/
Sheet Protection extension for Spreadsheet::WriteExcel::Worksheet
----
Spreadsheet-WriteExcel-Worksheet-SheetProtection-0.03
http://search.cpan.org/~sriha/Spreadsheet-WriteExcel-Worksheet-SheetProtection-0.03/
Sheet Protection extension for Spreadsheet::WriteExcel::Worksheet
----
Tie-DiskUsage-0.19
http://search.cpan.org/~schubiger/Tie-DiskUsage-0.19/
Tie disk-usage to a hash
----
Time-Fake-0.11
http://search.cpan.org/~rosulek/Time-Fake-0.11/
Simulate different times without changing your system clock
----
WWW-Ohloh-API-0.0.4
http://search.cpan.org/~yanick/WWW-Ohloh-API-0.0.4/
Ohloh API implementation
----
Win32-GUITaskAutomate-0.01
http://search.cpan.org/~zoffix/Win32-GUITaskAutomate-0.01/
A module for automating GUI tasks.
----
Workflow-XPDL-0.40
http://search.cpan.org/~srhoton/Workflow-XPDL-0.40/
Perl extension for reading XDPL
----
Yahoo-Lifestyle-0.2
http://search.cpan.org/~hcchien/Yahoo-Lifestyle-0.2/
is a simple interface for Yahoo! Taiwan Lifestyle open APIs. And you will need the Yahoo::BBAuth for some authentication APIs. Before you use that, you have to register a appid and secret for APIs req
----
deskpad-0.74
http://search.cpan.org/~rkies/deskpad-0.74/
A desktop calendar program like xcalendar.
If you're an author of one of these modules, please submit a detailed
announcement to comp.lang.perl.announce, and we'll pass it along.
This message was generated by a Perl program described in my Linux
Magazine column, which can be found on-line (along with more than
200 other freely available past column articles) at
http://www.stonehenge.com/merlyn/LinuxMag/col82.html
print "Just another Perl hacker," # the original
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
------------------------------
Date: Fri, 18 Jan 2008 02:27:35 -0700
From: "Regan Revised" <invalid@invalid.net>
Subject: non nntp usenet
Message-Id: <1200647793_7419@sp12lax.superfeed.net>
How can Outlook Express pick up usenet messages that net::nntp can't?
--
Reagan Revision
To sum up: 1. The cosmos is a gigantic fly-wheel making 10,000 revolutions a
minute. 2. Man is a sick fly taking a dizzy ride on it. 3. Religion is the
theory that the wheel was designed and set spinning to give him the ride.
-- H L Mencken, "Coda," in Smart Set (New York, Dec. 1920; repr. in A
Mencken Chrestomathy, pt. 1, 1949).
------------------------------
Date: Fri, 18 Jan 2008 08:13:45 GMT
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
Message-Id: <ZcZjj.40122$Pv2.25550@newssvr23.news.prodigy.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.8 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://www.rehabitation.com/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume that they do
know and are being the "bad kind" of Lazy.
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.noitatibaher\100cmdat/"
------------------------------
Date: Thu, 17 Jan 2008 19:11:18 -0800 (PST)
From: Rajpreet <rajpreetsidhu@gmail.com>
Subject: Re: Problem directing BCP Error to Error file
Message-Id: <8ef2662a-fcc3-433b-9ae6-8a4fc57816aa@v17g2000hsa.googlegroups.com>
On Jan 16, 10:54=A0pm, Jim Gibson <jimsgib...@gmail.com> wrote:
> In article
> <b24d11cb-5c7d-4532-9809-ab737876e...@f10g2000hsf.googlegroups.com>,
>
> Rajpreet <rajpreetsi...@gmail.com> wrote:
> > Greetings,
>
> > I am trying to bcp in data to a table which is in different server.
> > Though the bcp in works fine but the error file is not being created
> > and rejected records are not being directyd to =A0the error file. Query
> > looks like:
>
> > bcp <db>..test_b_plan_cp in /home/file_out.txt -c -t '|' -S *****-U
> > ****** -P ******-I /home/bcp2db_sql.ini =A0-e /home/bcp2db.error.
>
> > Can someone please help?
>
> Why are you asking questions about bcp in a Perl newsgroup? You were
> helped with your Perl problems a week ago, but it seems the problem you
> are having now is strictly with bcp.
>
> --
> Jim Gibson
>
> =A0Posted Via Usenet.com Premium Usenet Newsgroup Services
> ----------------------------------------------------------
> =A0 =A0 ** SPEED ** RETENTION ** COMPLETION ** ANONYMITY **
> ---------------------------------------------------------- =A0 =A0 =A0 =A0=
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0http://www.usenet.com
Sorry for the inconvenience caused. Actually the reason I posted it
here because I was trying to do bcp from within a perl script and
there in I was facing issues.
Is there any alternative to it? And can we use Sybase::BCP module
using an ini file?
TIA
------------------------------
Date: Thu, 17 Jan 2008 22:10:18 -0800 (PST)
From: clearguy02@yahoo.com
Subject: Re: To update one file with the another file's data..
Message-Id: <08d6e279-bfd0-4fd1-9dea-947c2b360f68@e6g2000prf.googlegroups.com>
On Jan 17, 5:53 pm, David Filmer <use...@davidfilmer.com> wrote:
> Gunnar Hjalmarsson wrote:
> >>> my ( $key, $value ) = split ' ', $_, 2;
> > --------------------------------------------^
> > Please note the LIMIT argument.
>
> Ah. I had noted it, but had forgotten exactly how it behaved. I was
> thinking it split everything and then returned only the first two
> splits. Thanks for refreshing my memory on how this limit (which I
> seldom use) actually behaves.
Thnks to every one.
J
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc. For subscription or unsubscription requests, send
#the single line:
#
# subscribe perl-users
#or:
# unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.
NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 1210
***************************************
