File: declare.l.html

package info (click to toggle)
mpsql 2.0-2
  • links: PTS
  • area: non-free
  • in suites: slink
  • size: 2,912 kB
  • ctags: 5,665
  • sloc: ansic: 34,322; makefile: 3,525; sh: 17
file content (54 lines) | stat: -rw-r--r-- 2,200 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
<!-- manual page source format generated by PolyglotMan v3.0.4, -->
<!-- available via anonymous ftp from ftp.cs.berkeley.edu:/ucb/people/phelps/tcltk/rman.tar.Z -->

<HTML>
<HEAD>
<TITLE>FETCH(SQL) manual page</TITLE>
</HEAD>
<BODY>
<A HREF="sql.html">SQL Reference Contents</A>
 
<H2><A NAME="sect0" HREF="#toc0">NAME </A></H2>
declare - declare a cursor  
<H2><A NAME="sect1" HREF="#toc1">SYNOPSIS </A></H2>
<B>declare </B> [ <B>binary </B> ] <B>cursor 
for </B> select statement <BR>
  
<H2><A NAME="sect2" HREF="#toc2">DESCRIPTION </A></H2>
<B>Declare</B> allows a user to create cursors. 
Cursors are only available in transactions. <P>
Normal cursors return data 
back in ASCII format.  Since data is stored natively in binary format, 
the system must do a conversion to produce the ASCII format.  In addition, 
ASCII formats are often larger in size than binary format.  Once the attributes 
come back in ASCII, often the client application then has to convert it 
to a binary format to manipulate it anyway. <P>
<B>Binary </B> cursors give you back 
the data in the native binary representation.  Thus, binary cursors will 
tend to be a little faster since there's less overhead of conversion. <P>
However, 
ASCII is architectural neutral whereas binary representation can differ 
between different machine architecture.  Thus, if your client machine uses 
a different representation than you server machine, getting back attributes 
in binary format is probably not what you want. Also, if your main purpose 
is displaying the data in ASCII, then getting it back in ASCII will save 
you some effort on the client side. <P>
For an example, see the <A HREF="fetch.l.html">fetch(l)</A>
 manual 
page.  
<H2><A NAME="sect3" HREF="#toc3">SEE ALSO </A></H2>
<A HREF="fetch.l.html">fetch(l)</A>
, <A HREF="begin.l.html">begin(l)</A>
, <A HREF="end.l.html">end(l)</A>
, <A HREF="select.l.html">select(l)</A>
. <P>

<HR><P>
<A NAME="toc"><B>Table of Contents</B></A><P>
<UL>
<LI><A NAME="toc0" HREF="#sect0">NAME</A></LI>
<LI><A NAME="toc1" HREF="#sect1">SYNOPSIS</A></LI>
<LI><A NAME="toc2" HREF="#sect2">DESCRIPTION</A></LI>
<LI><A NAME="toc3" HREF="#sect3">SEE ALSO</A></LI>
</UL>
</BODY></HTML>