The Scanner class (java.util.Scanner) is used to read data into your program. See the Java API for more information on the class Scanner
Here are some commonly used Scanner methods:
next() - read as String up the the blank space delimiter
nextLine() - read a String to the end of the line, including spaces
nextInt() - read an integer
nextDouble() - read a double (floating point number)
nextBoolean() - read a boolean
nextLong() - read a long
nextByte() - read a byte
nextShort() - read a short
next().charAt(0) - read the first character of a string (char)
Please SUBSCRIBE to Appficial, and check out more Java Programming Tutorials! http://www.appficial.com
The Basic Parts of a Java Program - Class and Main Method Header and Comments
Java Declaring and Initializing Variables
Naming Java Identifiers - Variables, Methods, and Object Names - Java Tutorial
Java Reserved Keywords - Words like public static void class int double
Java Primitive Data Types - byte short int long float double char and boolean
Java Integers - int long byte and short Integer Variables
Java Floating Point Numbers - float and double
Java E Notation - Doing Scientific Notation in a Java Program
Java Integer Division and Dividing by Zero - Java Tutorial - Appficial
Java Basic Math Arithmetic Expressions and Precedence Rules
Java Compound Operators - Combined Assignment Arithmetic Operator Examples
Java Constants - Constant Variables using Keyword Final
Java Math Class Methods
Java Type Conversions and Type Casting
How to Convert Binary numbers to Decimal Numbers
Java Characters - The char Primitive Data Type
Java Escape Characters
Java String Class
Java Scanner Class
Java Integer Overflow
Java Style Guidelines
A trigger is a named PL/SQL unit that is stored in the database and executed ( fired ) in response to a specified event that occurs in the database.
Overview of Triggers.
A trigger is a named program unit that is stored in the database and fired (executed) in response to a specified event. The specified event is associated with either a table, a view, a schema, or the database, and it is one of the following:
A database manipulation (DML) statement ( DELETE , INSERT , or UPDATE )
A database definition (DDL) statement ( CREATE , ALTER , or DROP )
A database operation ( SERVERERROR , LOGON , LOGOFF , STARTUP , or SHUTDOWN )
The trigger is said to be defined on the table, view, schema, or database.
A DML trigger is fired by a DML statement, a DDL trigger is fired by a DDL statement, a DELETE trigger is fired by a DELETE statement, and so on.
An INSTEAD OF trigger is a DML trigger that is defined on a view (not a table). The database fires the INSTEAD OF trigger instead of executing the triggering DML statement. For more information, see Modifying Complex Views (INSTEAD OF Triggers).
A system trigger is defined on a schema or the database. A trigger defined on a schema fires for each event associated with the owner of the schema (the current user). A trigger defined on a database fires for each event associated with all users.
A simple trigger can fire at exactly one of the following timing points :
Before the triggering statement executes.
After the triggering statement executes.
Before each row that the triggering statement affects.
After each row that the triggering statement affects.
A compound trigger can fire at more than one timing point. Compound triggers make it easier to program an approach where you want the actions you implement for the various timing points to share common data. For more information, see Compound Triggers.