Here is a slightly different approach that seems to work:
If you want to try this on a Solaris/SunOS system, change awk to /usr/xpg4/bin/awk or nawk.
In addition to the output you said should be produced from your sample log.txt file, it also prints the output:
Is there some reason why these lines should have been deleted from the output?
This User Gave Thanks to Don Cragun For This Post:
how to use "tr" command to display horizontal line to vertical line
for vertical to horizontal, the command is tr '\n' '\t' <inputfile
but what is the command for horizontal to vertical
Thanks
Vasikaran (3 Replies)
Hi,
I have a file like below
robert
PREF: 3
AVAIL:
henry
PREF: 234
AVAIL:
john
PREF: 145,178
AVAIL: 123
matt
PREF: 564,932
AVAIL:
ten
PREF: 389
AVAIL: kill (2 Replies)
Hi,
Silly question, if I have an excel file that looks something like this:
................. Subject 1 Subject 2 Subject 3 Subject 4
Fever..............13...........9.............23..........14
Headache.........2............12...........18..........23... (3 Replies)
How to move a vertical line to Horizontal line.....Can i use a tr command?
code is:
StudentID
Java
.Net
C#
I want to move this line like this:
StudentID Java .Net C#
Please use
code tags! (3 Replies)
Need perl or shell script to sort vertical lines to horizontal line in csv format
My file like below
-------------------------
================================================================================
PATH PINKY1000#I1-1-ZENTA1000-2#I7-1-ASON-SBR-UP-943113845 ... (4 Replies)
Hi,
I have log like this :
And i want the output like below :
I have try using awk but doesn't work
awk '
/ffff /{ts=$1}
f && /SectorAntenna\=1/{sa1=$3}
f && /SectorAntenna\=2/{sa2=$3}
f && /SectorAntenna\=3/{sa3=$3}
{
s= ts "|" sa1 "|" sa2 "|" sa3
print s
f=0
}' (7 Replies)
BEGIN(7) SQL Commands BEGIN(7)NAME
BEGIN - start a transaction block
SYNOPSIS
BEGIN [ WORK | TRANSACTION ] [ transaction_mode [, ...] ]
where transaction_mode is one of:
ISOLATION LEVEL { SERIALIZABLE | REPEATABLE READ | READ COMMITTED | READ UNCOMMITTED }
READ WRITE | READ ONLY
DESCRIPTION
BEGIN initiates a transaction block, that is, all statements after a BEGIN command will be executed in a single transaction until an
explicit COMMIT [commit(7)] or ROLLBACK [rollback(7)] is given. By default (without BEGIN), PostgreSQL executes transactions in ``autocom-
mit'' mode, that is, each statement is executed in its own transaction and a commit is implicitly performed at the end of the statement (if
execution was successful, otherwise a rollback is done).
Statements are executed more quickly in a transaction block, because transaction start/commit requires significant CPU and disk activity.
Execution of multiple statements inside a transaction is also useful to ensure consistency when making several related changes: other ses-
sions will be unable to see the intermediate states wherein not all the related updates have been done.
If the isolation level or read/write mode is specified, the new transaction has those characteristics, as if SET TRANSACTION [set_transac-
tion(7)] was executed.
PARAMETERS
WORK
TRANSACTION
Optional key words. They have no effect.
Refer to SET TRANSACTION [set_transaction(7)] for information on the meaning of the other parameters to this statement.
NOTES
START TRANSACTION [start_transaction(7)] has the same functionality as BEGIN.
Use COMMIT [commit(7)] or ROLLBACK [rollback(7)] to terminate a transaction block.
Issuing BEGIN when already inside a transaction block will provoke a warning message. The state of the transaction is not affected. To
nest transactions within a transaction block, use savepoints (see SAVEPOINT [savepoint(7)]).
For reasons of backwards compatibility, the commas between successive transaction_modes can be omitted.
EXAMPLES
To begin a transaction block:
BEGIN;
COMPATIBILITY
BEGIN is a PostgreSQL language extension. It is equivalent to the SQL-standard command START TRANSACTION [start_transaction(7)], whose ref-
erence page contains additional compatibility information.
Incidentally, the BEGIN key word is used for a different purpose in embedded SQL. You are advised to be careful about the transaction
semantics when porting database applications.
SEE ALSO
COMMIT [commit(7)], ROLLBACK [rollback(7)], START TRANSACTION [start_transaction(7)], SAVEPOINT [savepoint(7)]
SQL - Language Statements 2010-05-14 BEGIN(7)