I am an Oracle DBA who has been writing PL/SQL for over 15 years. You should not need to learn explicit cursors. Perhaps your instructor wants you to understand explicit cursors but you should use implicit cursors instead. You can't select from an explicit cursor so that line won't work. You can use the c1%ROWCOUNT attribute. You may want to look at PL/SQL collections.
dear friends,
I have a large size file containg two fields data
like this
*** ****
122 222
***** *****
***** *****
232 233
i have file like this.
i want to remove blank lines from file .
i think awk is servive this problem
i wrote a awk command but the error is... (3 Replies)
Dear friends,
I am writing shell script in csh .
i want to make arthimatic operation in csh.
i wrote sysntax like this.
set val = 230
set tmp = `0.1 * $val + 300`
echo $tmp
but it is not working .
anyone please give me syntax. (3 Replies)
m kinda new to unix. i have been trying to write a script where i am trying to switch between users.
but the problem is that the syntax like USERNAME/PASSWORD (like oracle SCOT/TIGER) is not working.
if i write su USERNAME then the script goes to the command prompt and asks for user to enter... (0 Replies)
I am calculating a time and appending a space in front of it to get only certain records in a file because the times are represented in HH:II:SS format and I don't want to see anything other than the actual hour and minute combination (hence appending the space to the front of the time). My... (9 Replies)
I have one File named "txt_file"
# cat txt_file
<DBType>RT</DBType>
<AppType>RT</AppType>
--------------------------------------------------
I want replace "<AppType>RT</AppType>" to
<AppType>XY</AppType> in txt_file and output redirect to Newfile
... (2 Replies)
Hi guys,
Basically I'm trying to write a CShell script that calls an awk script on a given directory (given in command-line). I keep getting a syntax error with my code though:
#!/bin/csh
set dir = $ARGV
foreach file ( $dir/* )
set output = 'awk -f /Desktop/aal $file'
echo... (3 Replies)
Hello,
I have perl script,which take some part of data in the file.
the below command works fine in normal cmd prompt.
`awk '/CDI/ && // && !/Result for/ {print $3 $5 > "final.txt"}' datalist.txt`;
`nawk -F"" '{print $2}' finalcdi.txt`;
But not working.
Please use code tags, thanks. (5 Replies)
I'm calling the following if-else from nawk. But I keep getting an error at the "else". I've tried putting more brackets and ; but still I get complaints about the "else".
Any ideas ?
Thanks,
wbrunc
BEGIN { FS = "," ; OFS = "," }
{ if ( $8 ~ /A/ && $9 == B )
$1="4/29/2013" ;
$2="J.Doe"... (2 Replies)
awk -v sw="lemons|dogs" 'NR>100 && NR<200 BEGIN { c=split(sw,a,""); } { for (w in a) { if ($0 ~ a) d]++; } }
END { for (i in a) { o=o (a"="(d]?d]:0)","); }
sub(",*$","",o); print o;
}' /home/jahitt/data.txt
what am i doing wrong with the above code? im pretty sure the issue is in the... (6 Replies)
Discussion started by: SkySmart
6 Replies
LEARN ABOUT REDHAT
declare
DECLARE(7) SQL Commands DECLARE(7)NAME
DECLARE - define a cursor
SYNOPSIS
DECLARE cursorname [ BINARY ] [ INSENSITIVE ] [ SCROLL ]
CURSOR FOR query
[ FOR { READ ONLY | UPDATE [ OF column [, ...] ] ]
INPUTS
cursorname
The name of the cursor to be used in subsequent FETCH operations.
BINARY Causes the cursor to fetch data in binary rather than in text format.
INSENSITIVE
SQL92 keyword indicating that data retrieved from the cursor should be unaffected by updates from other processes or cursors. Since
cursor operations occur within transactions in PostgreSQL this is always the case. This keyword has no effect.
SCROLL SQL92 keyword indicating that data may be retrieved in multiple rows per FETCH operation. Since this is allowed at all times by
PostgreSQL this keyword has no effect.
query An SQL query which will provide the rows to be governed by the cursor. Refer to the SELECT statement for further information about
valid arguments.
READ ONLY
SQL92 keyword indicating that the cursor will be used in a read only mode. Since this is the only cursor access mode available in
PostgreSQL this keyword has no effect.
UPDATE SQL92 keyword indicating that the cursor will be used to update tables. Since cursor updates are not currently supported in Post-
greSQL this keyword provokes an informational error message.
column Column(s) to be updated. Since cursor updates are not currently supported in PostgreSQL the UPDATE clause provokes an informational
error message.
OUTPUTS
DECLARE CURSOR
The message returned if the SELECT is run successfully.
WARNING: Closing pre-existing portal "cursorname"
This message is reported if the same cursor name was already declared in the current transaction block. The previous definition is
discarded.
ERROR: DECLARE CURSOR may only be used in begin/end transaction blocks
This error occurs if the cursor is not declared within a transaction block.
DESCRIPTION
DECLARE allows a user to create cursors, which can be used to retrieve a small number of rows at a time out of a larger query. Cursors can
return data either in text or in binary format using FETCH [fetch(7)].
Normal cursors return data in text format, either ASCII or another encoding scheme depending on how the PostgreSQL backend was built. Since
data is stored natively in binary format, the system must do a conversion to produce the text format. In addition, text formats are often
larger in size than the corresponding binary format. Once the information comes back in text form, the client application may need to con-
vert it to a binary format to manipulate it. BINARY cursors give you back the data in the native binary representation.
As an example, if a query returns a value of one from an integer column, you would get a string of 1 with a default cursor whereas with a
binary cursor you would get a 4-byte value equal to control-A (^A).
BINARY cursors should be used carefully. User applications such as psql are not aware of binary cursors and expect data to come back in a
text format.
String representation is architecture-neutral whereas binary representation can differ between different machine architectures. PostgreSQL
does not resolve byte ordering or representation issues for binary cursors. Therefore, if your client machine and server machine use dif-
ferent representations (e.g., ``big-endian'' versus ``little-endian''), you will probably not want your data returned in binary format.
However, binary cursors may be a little more efficient since there is less conversion overhead in the server to client data transfer.
Tip: If you intend to display the data in ASCII, getting it back in ASCII will save you some effort on the client side.
NOTES
Cursors are only available in transactions. Use to BEGIN [begin(7)], COMMIT [commit(7)] and ROLLBACK [rollback(7)] to define a transaction
block.
In SQL92 cursors are only available in embedded SQL (ESQL) applications. The PostgreSQL backend does not implement an explicit OPEN cursor
statement; a cursor is considered to be open when it is declared. However, ecpg, the embedded SQL preprocessor for PostgreSQL, supports
the SQL92 cursor conventions, including those involving DECLARE and OPEN statements.
USAGE
To declare a cursor:
DECLARE liahona CURSOR
FOR SELECT * FROM films;
COMPATIBILITY
SQL92
SQL92 allows cursors only in embedded SQL and in modules. PostgreSQL permits cursors to be used interactively. SQL92 allows embedded or
modular cursors to update database information. All PostgreSQL cursors are read only. The BINARY keyword is a PostgreSQL extension.
SQL - Language Statements 2002-11-22 DECLARE(7)