04-22-2008
So far so good. You've connected to the DB...
Is the deletion business logic simple enough to be done in a single DML statement? For example...
DELETE from TABLENAME T where T.SOMEDATE <= (sysdate() - 7) and T.FREEFLAG = TRUE;
I don't know mysql so I'm giving a generic kind of syntax here... If the issue is not that simple, then you need to issue an appropriate SELECT statement, capture the results in perl, analyze them, and then issue delete statements on the appropriate rows... I haven't used the DBI in a while, so I don't remember the exact syntax of passing DML statements to the DBI, but in PERL, the results of the statement can be captured automatically in an array... Again I'm going to illustrate with "pseudo syntax". You translate into something that actually works...
$statement_to_exec = "SELECT X,Y,Z from T where Z...;"
(@myARRAY) = $myconnect->execute($statement_to_exec);
Now suppose you have properly set up your select statement so that the data comes out like this....
A,B,C
D,E,F
G,H,I
etc... That is, fields separated by commas (just as an example) and each record on its own line... So guess what.... $myARRAY[0] = "A,B,C" and $myARRAY[1] = "D,E,F" etc. That is each record is put in a separate element of @myARRAY! I'm assuming here that you've left perl's default line ending character alone, that the lines end with that (usual) character, etc. You can control all of this, but usually it isn't necessary....
OK, so now you can iterate over each line...
while ($line = shift @myARRAY) { ... logic here ... }
And then, you can split line into it's separate fields with....
($field1, $field2, $field3) = split /,/ , $line;
Now $field1 = "A", $field2 = "B", etc.
This is how you proceede... When you decide which lines must be deleted, say the line in $myARRAY[2] (the third line), then you issue a DELETE via the DBI for that line only....
As for the cron line, that is very easy. Just edit a file in your home directory called myCRONTAB (sysadmins might want you to use a system CRONTAB, or some other established one) and put a line in it like....
0 0 * * * /path/to/your/script.pl (says run at 0 min of 0 hr every day, I'll let you look up cron syntax for yourself)...
Then set up the job by entering cron myCRONTAB and if there are no syntax errors in the file, your good to go...
Oh... One more thing to remember.... when you run a script from cron it has NO ENVIRONMENT... So, you can't rely on PATH, or anything else. You have to set all that stuff up in your perl script....
Long I know, but I hope it helps....
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Is there a way to determine if a Script is called from a
CRON job or from a commandline
Gerry. (2 Replies)
Discussion started by: jerryMcguire
2 Replies
2. UNIX for Dummies Questions & Answers
Dear all
How can I schedule the cronjob to be run sometime at every first Sunday at every month? I have the edit the cronjob every month now, thanks (2 Replies)
Discussion started by: shanemcmahon
2 Replies
3. UNIX for Dummies Questions & Answers
Hi everyone:
I'm trying to make a CRON job that will execute Fridays at 7am. I have the following:
* 7 * * 5
I've been studying up on CRON and I know to have this in a file and then "crontab filename.txt" to add it to the CRON job list.
The CRON part I believe I understand, but I would... (6 Replies)
Discussion started by: Annorax
6 Replies
4. UNIX for Advanced & Expert Users
Although there are many threads on this forum regarding cron, none have specifically answered my question. So hopefully someone can shed some light on what I'm doing wrong..
I have a perl script that I want to run in a cron job. Since I've read that cron doesn't have any environments set, I... (3 Replies)
Discussion started by: man
3 Replies
5. Solaris
Hi,
I want to run a crontab job on solaris 10.5. I have configured the crontab accordingly
10 * * * * /scripts/dbalter.pl >> /scripts/cronout.txt
However this does not work .Then I go to /var/mail/root and find an error in the output:
From root@myserver Wed Feb 4 17:02:00 2009... (1 Reply)
Discussion started by: sonu2die4
1 Replies
6. Shell Programming and Scripting
Hello All,
I am getting the following error message when trying to execute the following script.
AWK=/usr/bin/awk
TR=/usr/bin/tr
SED=/usr/bin/sed
CAT=/usr/bin/cat
MAILFILE=/home//nightly_jobs.tmp
mailto=xxx@gmail.com
Nigh_Status = `db2 "select TYPE from ETL.LOCK where STATUS <> 0 and... (12 Replies)
Discussion started by: NARESH1302
12 Replies
7. Shell Programming and Scripting
I am trying to get the string containing date - in a specfic format actually, although I think that part is inconsequencial - 1110226^1110226^1110226^1110226^1110226 - through echo or printf or in some other way - created within a cront job and passed as a parameter to a perl script.
Now, I know... (3 Replies)
Discussion started by: v8625
3 Replies
8. Shell Programming and Scripting
Hi
I want to execute a cron job everyday at 14:50 hrs. I have a script like this:
TMP_FILE="/tmp/tmpcron.txt"
RES=0
/usr/bin/crontab -l >> $TMP_FILE
ADD_JOB="50 14 * * * /opt/mypath/scriptname.sh"
grep "scriptname.sh" $TMP_FILE >> /dev/null
JOB_NOT_EXIST=$?
if test $JOB_NOT_EXIST... (2 Replies)
Discussion started by: saurabhkoar
2 Replies
9. Shell Programming and Scripting
Hello,
When I'm trying to send bsub job using script that executes fine in command line, I get nothing.
I do this for testing purposes, and the script scr_test is just one line:
pwd > outfile
So when I'm executing it in command line:
$ ./scr_test
it works fine producing the outfile with... (2 Replies)
Discussion started by: Sergey Aliev
2 Replies
10. Programming
I have reviewed many examples on-line about running another process (either PERL or shell command or a program), but do not find any usefull for my needs way. (Reviewed and not useful the system(), 'back ticks', exec() and open())
I would like to run another PERL-script from first one, not... (1 Reply)
Discussion started by: alex_5161
1 Replies
PDO.EXEC(3) 1 PDO.EXEC(3)
PDO
::exec - Execute an SQL statement and return the number of affected rows
SYNOPSIS
public int PDO::exec (string $statement)
DESCRIPTION
PDO.exec(3) executes an SQL statement in a single function call, returning the number of rows affected by the statement.
PDO.exec(3) does not return results from a SELECT statement. For a SELECT statement that you only need to issue once during your program,
consider issuing PDO.query(3). For a statement that you need to issue multiple times, prepare a PDOStatement object with PDO.prepare(3) and
issue the statement with PDOStatement.execute(3).
PARAMETERS
o $statement
- The SQL statement to prepare and execute. Data inside the query should be properly escaped.
RETURN VALUES
PDO.exec(3) returns the number of rows that were modified or deleted by the SQL statement you issued. If no rows were affected, PDO.exec(3)
returns 0.
Warning
This function may return Boolean FALSE, but may also return a non-Boolean value which evaluates to FALSE. Please read the section on
Booleans for more information. Use the === operator for testing the return value of this function.
The following example incorrectly relies on the return value of PDO.exec(3), wherein a statement that affected 0 rows results in a call to
die(3):
<?php
$db->exec() or die(print_r($db->errorInfo(), true));
?>
EXAMPLES
Example #1
Issuing a DELETE statement
Count the number of rows deleted by a DELETE statement with no WHERE clause.
<?php
$dbh = new PDO('odbc:sample', 'db2inst1', 'ibmdb2');
/* Delete all rows from the FRUIT table */
$count = $dbh->exec("DELETE FROM fruit WHERE colour = 'red'");
/* Return number of rows that were deleted */
print("Deleted $count rows.
");
?>
The above example will output:
Deleted 1 rows.
SEE ALSO
PDO.prepare(3), PDO.query(3), PDOStatement.execute(3).
PHP Documentation Group PDO.EXEC(3)