Oracle SQL Developer

More documents

Recommendations

Info

Storing Numeric DataThe absence of precision and scale designators specifies the maximum range andprecision for an Oracle number.Table 5–1 show how Oracle stores data using different values for precision and scale.Table 5–1Storage of Scale and PrecisionActual Data Specified As Stored As123.89 NUMBER 123.89123.89 NUMBER(3) 124123.89 NUMBER(6,2) 123.89123.89 NUMBER(6,1) 123.9123.89 NUMBER(3) exceeds precision123.89 NUMBER(4,2) exceeds precision123.89 NUMBER(6,-2) 100.01234 NUMBER(4,5) .01234.00012 NUMBER(4,5) .00012.000127 NUMBER(4,5) .00013.0000012 NUMBER(2,7) .0000012.00000123 NUMBER(2,7) .00000121.2e-4 NUMBER(2,5) 0.000121.2e-5 NUMBER(2,5) 0.000015.3.3 Using Floating-Point Number FormatsThe BINARY_FLOAT and BINARY_DOUBLE data types store floating-point data in the32-bit IEEE 754 format and the double precision 64-bit IEEE 754 format respectively.Compared to the Oracle NUMBER data type, arithmetic operations on floating-pointdata are usually faster for BINARY_FLOAT and BINARY_DOUBLE. Also, high-precisionvalues require less space when stored as BINARY_FLOAT and BINARY_DOUBLE.The floating-point number system is a common way of representing and manipulatingnumeric values in computer systems. The value 4.32682E-21F is an example of aBINARY_FLOAT data type.Floating-point numbers can have a decimal point anywhere from the first to the lastdigit or can have no decimal point at all. An exponent may optionally be usedfollowing the number to increase the range (for example, 1.777 e -20 ). A scale value isnot applicable to floating-point numbers, because the number of digits that can appearafter the decimal point is not restricted.Binary floating-point numbers differ from NUMBER in the way the values are storedinternally by Oracle Database. Values are stored using decimal precision for NUMBER.All literals that are within the range and precision supported by NUMBER are storedexactly as NUMBER. Literals are stored exactly because literals are expressed usingdecimal precision (the digits 0 through 9). Binary floating-point numbers are storedusing binary precision (the digits 0 and 1). Such a storage scheme cannot represent allvalues using decimal precision exactly. Frequently, the error that occurs whenconverting a value from decimal to binary precision is undone when the value isconverted back from binary to decimal precision. The literal 0.1 is such an example.5-4 SQL Developer Online Help
Storing Datetime Data5.3.3.1 BINARY_FLOATBINARY_FLOAT is a 32-bit, single-precision floating-point number data type. EachBINARY_FLOAT value requires 5 bytes, including a length byte.5.3.3.2 BINARY_DOUBLEBINARY_DOUBLE is a 64-bit, double-precision floating-point number data type. EachBINARY_DOUBLE value requires 9 bytes, including a length byte.In a NUMBER column, floating point numbers have decimal precision. In a BINARY_FLOAT or BINARY_DOUBLE column, floating-point numbers have binary precision.The binary floating-point numbers support the special values infinity and NaN (not anumber).You can specify floating-point numbers within the limits listed in Table 5–2 onpage 5-5.Table 5–25.4 Storing Datetime DataThis topic contains the following topics:■■Using DATE and TIMESTAMP Data TypesManipulating the DATE and TIME Formats5.4.1 Using DATE and TIMESTAMP Data TypesOracle Database supports the following datetime data types:■■■■DATETIMESTAMPFloating Point Number LimitsValue Binary-Float Binary-DoubleMaximum positive finite value 3.40282E+38F 1.79769313486231E+308Minimum positive finite value 1.17549E-38F 2.22507485850720E-308TIMESTAMP WITH TIME ZONETIMESTAMP WITH LOCAL TIME ZONESee Also:■Oracle Database SQL Reference for information on DATE,TIMESTAMP, TIMESTAMP WITH TIME ZONE, and TIMESTAMPWITH LOCAL TIME ZONE data types5.4.1.1 Using the DATE Data TypeUse the DATE data type to store point-in-time values (dates and times) in a table. Anapplication that specifies the time for a job might use the DATE data type.The DATE data type stores the century, year, month, day, hours, minutes, and seconds.The valid date range is from January 1, 4712 BC to December 31, 9999 AD.Data Types: Usage Information 5-5
Page 1 and 2:
Oracle SQL DeveloperOnline HelpRele
Page 3 and 4:
Contents1 SQL Developer Concepts an
Page 5 and 6:
3.12 Create/Edit Index ............
Page 7 and 8:
6.3.2 Updating Data With the UPDATE
Page 9:
10.2.5 SQL*Plus SET Commands.......
Page 12 and 13:
SQL Developer User InterfaceThe men
Page 14 and 15:
SQL Developer User InterfaceThe Com
Page 16 and 17:
Database Objects1.2 Database Object
Page 18 and 19:
Database Objectscontaining the mast
Page 20 and 21:
Database Objects■■■■■■
Page 22 and 23:
Database ConnectionsWhen you start
Page 24 and 25:
Running and Debugging Functions and
Page 26 and 27:
Using the SQL WorksheetRelated Topi
Page 28 and 29:
Using the SQL WorksheetScript Runne
Page 30 and 31:
Using the SQL Worksheetmentioned in
Page 32 and 33:
Reports1.9 ReportsRelated TopicsRun
Page 34 and 35:
Reports1.9.3 Table reportsTable rep
Page 36 and 37:
Reportsissues and vulnerabilities,
Page 38 and 39:
SQL Developer Preferencesand the SQ
Page 40 and 41:
SQL Developer Preferences1.10.3 Cod
Page 42 and 43:
SQL Developer PreferencesSQL Develo
Page 44 and 45:
SQL Developer User Information: Loc
Page 46 and 47:
Supplementary Oracle Database Infor
Page 48 and 49:
Creating a Table (Books)the table t
Page 50 and 51:
Creating a Table (Transactions)Colu
Page 52 and 53:
Creating a SequenceName: for_key_bo
Page 54 and 55: Creating a PL/SQL Procedure2.6 Crea
Page 56 and 57: Using the SQL Worksheet for Queries
Page 58 and 59: Script for Creating and Using the L
Page 60 and 61: Script for Creating and Using the L
Page 62 and 63: Check for UpdatesTo remove the effe
Page 64 and 65: Select Library3.8 Select LibraryThi
Page 66 and 67: Create PL/SQL Function, Procedure,
Page 68 and 69: Create Table (quick creation)Relate
Page 70 and 71: Create/Edit Table (with advanced op
Page 78 and 79: Create Type (User-Defined)For more
Page 80 and 81: Create/Edit ViewTest Syntax: Checks
Page 82 and 83: Configure File Type AssociationsDia
Page 84 and 85: Find/Replace TextTo add a type of o
Page 86 and 87: Save/Save As3.37 Save/Save As3.38 S
Page 88 and 89: SQL*Plus Location3-28 SQL Developer
Page 90 and 91: Managing TablesTo include lowercase
Page 92 and 93: Managing Tables4.2.4 Column Constra
Page 94 and 95: Managing Indexes4.3 Managing Indexe
Page 96 and 97: Managing Indexesuseful when all of
Page 98 and 99: Managing Views4.4 Managing Views4.3
Page 100 and 101: Managing Synonyms4-12 SQL Developer
Page 102 and 103: Storing Numeric Data■■NCHAR and
Page 106 and 107: Storing Datetime Data5.4.1.2 Using
Page 108 and 109: Storing Datetime Data5-8 SQL Develo
Page 110 and 111: Retrieving Data With Queries■■
Page 112 and 113: Retrieving Data With QueriesSee Als
Page 114 and 115: Retrieving Data With QueriesSee Als
Page 116 and 117: Transaction Control Statements6.3.2
Page 118 and 119: Using Pseudocolumns, Sequences, and
Page 124 and 125: Using SQL Data Definition Language
Page 126 and 127: Using SQL Data Definition Language
Page 128 and 129: Entering and Executing PL/SQL CodeY
Page 130 and 131: Utilizing the Main Features of PL/S
Page 148 and 149: Handling PL/SQL ErrorsTo handle une
Page 150 and 151: Handling PL/SQL ErrorsIf you redecl
Page 152 and 153: Handling PL/SQL Errors7-26 SQL Deve
Page 154 and 155:
Overview of Packages and Subprogram
Page 156 and 157:
Managing Packagescalling procedures
Page 158 and 159:
Oracle Product-Specific PackagesTab
Page 160 and 161:
Oracle Product-Specific PackagesTab
Page 162 and 163:
Oracle Product-Specific Packages8-1
Page 164 and 165:
Overview of Triggers9.1.1 Types of
Page 166 and 167:
Overview of Triggers■■A trigger
Page 168 and 169:
Designing TriggersNote: A procedure
Page 170 and 171:
Using SQL*Plus■■■Running Scri
Page 172 and 173:
Using SQL*PlusA SQL script file is
Page 174 and 175:
Using SQL*Plus10-6 SQL Developer On
Page 176 and 177:
Overview of Globalization Support
Page 178 and 179:
Setting up the Globalization Suppor
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
SQL and PL/SQL Programming with Uni
Page 194 and 195:
SQL and PL/SQL Programming with Uni
Page 196 and 197:
Locale-Dependent SQL Functions with
Page 198 and 199:
Locale-Dependent SQL Functions with
Page 200 and 201:
COLLECTION_IS_NULL exception, 7-22c
Page 202 and 203:
overview, 7-14EXPLAIN PLANexecution
Page 204 and 205:
NLSSORT SQL function, 11-21NO_DATA_
Page 206 and 207:
displaying output from PL/SQL, 7-9s
Page 208:
disabling, 9-4enabling, 9-4error co
show all

Oracle SQL Developer

Create successful ePaper yourself

Delete template?

Save as template?