ShareThis

JavaScript Email Validation, Radio Button Validation

Here is a Javascript example for validate an email address and validate radio buttons on a form. For the radio buttons it will check that, one has selected and returns which one has selected.


function validateInputs()
{
errText = "";

uSignUpEmail = document.getElementById('txtSignUpEmail').value;
if ((uSignUpEmail.length <= 0) || (emailCheck(uSignUpEmail)==false))
{
errText = errText + '

Your Email address will be used as you site login please make sure that you have entered it correctly.

';

}

uRadioAge = frmUserSignUp.radioAge;
if(uRadioAge)
{
if(valRadioButton(uRadioAge)==null)
{
errText = errText + '

Please let us know if you are over 18.

';

valid = false;
}
}

document.getElementById('validationSummary').innerHTML = errText;
}


// Email Address Validation
function emailCheck(str)
{
var at="@";
var dot=".";
var lat=str.indexOf(at);
var lstr=str.length;
var ldot=str.indexOf(dot);
if (str.indexOf(at)==-1)
{
return false;
}
if (str.indexOf(at)==-1 || str.indexOf(at)==0 || str.indexOf(at)==lstr)
{
return false;
}
if (str.indexOf(dot)==-1 || str.indexOf(dot)==0 || str.indexOf(dot)==lstr)
{
return false;
}
if (str.indexOf(at,(lat+1))!=-1)
{
return false;
}
if (str.substring(lat-1,lat)==dot || str.substring(lat+1,lat+2)==dot)
{
return false;
}
if (str.indexOf(dot,(lat+2))==-1)
{
return false;
}
if (str.indexOf(" ")!=-1)
{
return false;
}
return true;
}


// Radio Button Validation
function valRadioButton(btn)
{
var cnt = -1;
for (var i=btn.length-1; i > -1; i--)
{
if (btn[i].checked)
{
cnt = i; i = -1;
}
}
if (cnt > -1)
{
return btn[cnt].value;
}
else
{
return null;
}
}

HTML Code

input name="txtSignUpEmail" type="text" class="formtextbox" id="txtSignUpEmail" />

I am 18 years of age or older
input name="radioAge" type="radio" value="true" id="radioAge1" />
Yes
input name="radioAge" type="radio" value="false" id="radioAge2" />
No

input name="Submit" id="Submit" type="image" onclick="return validateInputs();" src="Images/btSignup.jpg" width="111" height="31" />




SQL*Plus and Oracle

SQL*Plus is a command line SQL and PL/SQL language interface and reporting tool that ships with the Oracle Database Client and Server.

Connect to a Oracle (10g) Database using SQL*Plus

  • From the Start menu find SQL*Plus in oracle home (If you are going to connect from a remote machine you need to have an oracle client installed on it).
  • Give User Name, Password and Host string
    • If you haven’t created specific users, you can log using System or Sys accounts. Password is what you given in the installation. Host String is also asking from you in the configuration just after installation.
    • Anyhow if you forgot the Host String you can find it on the following location. “\oracle\product\10.2.0\client_1\NETWORK\ADMIN\tnsnames.ora” Here as I have noticed many times this oracle folder is not in the local drive which your Program Files folder exists. Just check other Local Drives as well. Inside tnsnames.ora file there should be a segment like follows.

      # tnsnames.ora Network Configuration File: D:\oracle\product\10.2.0\client_1\network\admin\tnsnames.ora
      # Generated by Oracle configuration tools.

      ORCL =
      (DESCRIPTION =
      (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.11)(PORT = 1521))
      )
      (CONNECT_DATA =
      (SERVICE_NAME = XE)
      )
      )

    • Here ORCL is the Host String. You can give any name for it as you like. SERVICE_NAME is XE for oracle express edition and orcl for oracle enterprise edition in default.
    • You can find exact value from Registry Editor of server machine in the following location.
    • HKEY_LOCAL_MACHINE – SOFTWARE – ORACLE – SYSMAN – OracleDBConsoleorcl – ORACLE_SID
  • After you connected to server you can get a list of tables using following command.

    • SQL> select * from tab;
  • 3 kinds of commands can be executed from SQL*Plus
    • SQL*Plus commands - used to set options for SQL*Plus, format reports, edit files, edit the command buffer, and so on
      • SHOW USER
    • SQL commands
      • SELECT * FROM TAB;
    • PL/SQL blocks
      • BEGIN
        DBMS_OUTPUT.PUT_LINE (‘Hello World!’);
        END;
        /

Development on Oracle 10g Packages, Stored procedures, Functions

An Oracle package is a schema object that groups logically related PL/SQL types, items and subprograms.

Packages have two parts, the specification and the body.

  • The specification is the interface into the package. It describes all the types, variables, procedures, etc within the package.
  • The body has all the implementation. Inside the body you would actually write the procedures, assign the values, and have all the details and logic behind the package.

Sample oracle package

Specification


create or replace PACKAGE ChallengePkg
IS

TYPE ref_cur_type

IS REF CURSOR;


PROCEDURE GetChallenge(ChallengeId IN CHALLENGE.ID%TYPE, challenge OUT ref_cur_type);


PROCEDURE GetChallenges(challenges OUT ref_cur_type);
PROCEDURE InsertChallenge(challengeId OUT CHALLENGE.ID%TYPE,
creationUserId IN CHALLENGE.CREATIONUSERID%TYPE,
publicId IN CHALLENGE.PUBLICID%TYPE,
creationDate IN CHALLENGE.CREATIONDATE%TYPE);


PROCEDURE UpdateChallenge(challengeId IN CHALLENGE.ID%TYPE,
argCreationUserId IN CHALLENGE.CREATIONUSERID%TYPE,
argPublicId IN CHALLENGE.PUBLICID%TYPE,
argCreationDate IN CHALLENGE.CREATIONDATE%TYPE);


PROCEDURE DeleteChallenge(challengeId IN CHALLENGE.ID%TYPE);


END ChallengePkg;


Body

create or replace PACKAGE BODY ChallengePkg
IS

PROCEDURE GetChallenge(ChallengeId IN CHALLENGE.ID%TYPE, challenge OUT ref_cur_type)
IS
BEGIN
OPEN challenge
FOR SELECT CHALLENGE.ID,CHALLENGE.CREATIONUSERID,CHALLENGE.PUBLICID, CHALLENGE.CREATIONDATE
FROM CHALLENGE
WHERE CHALLENGE.ID = ChallengeId;
END GetChallenge;


PROCEDURE GetChallenges(challenges OUT ref_cur_type)
IS

BEGIN
OPEN challenges
FOR SELECT CHALLENGE.ID,CHALLENGE.CREATIONUSERID,CHALLENGE.PUBLICID, CHALLENGE.CREATIONDATE
FROM CHALLENGE;
END GetChallenges;


PROCEDURE InsertChallenge(challengeId OUT CHALLENGE.ID%TYPE,
creationUserId IN CHALLENGE.CREATIONUSERID%TYPE,
publicId IN CHALLENGE.PUBLICID%TYPE,
creationDate IN CHALLENGE.CREATIONDATE%TYPE)

IS
BEGIN
INSERT INTO CHALLENGE(CREATIONUSERID,PUBLICID,CREATIONDATE)
VALUES (creationUserId,publicId,creationDate);
COMMIT;

SELECT CHALLENGE_SEQ.currval INTO challengeId FROM dual;

END InsertChallenge;


PROCEDURE UpdateChallenge(challengeId IN CHALLENGE.ID%TYPE,
argCreationUserId IN CHALLENGE.CREATIONUSERID%TYPE,
argPublicId IN CHALLENGE.PUBLICID%TYPE,
argCreationDate IN CHALLENGE.CREATIONDATE%TYPE)
IS
BEGIN
UPDATE CHALLENGE SET CREATIONUSERID = argCreationUserId, PUBLICID= argPublicId, CREATIONDATE = argCreationDate
WHERE ID = challengeId;
COMMIT;
END UpdateChallenge;


PROCEDURE DeleteChallenge(challengeId IN CHALLENGE.ID%TYPE)
IS
BEGIN
DELETE FROM CHALLENGE
WHERE ID = challengeId;
COMMIT;
END DeleteChallenge;

END ChallengePkg;


Some benefits of using packages

1. Objects don't get invalidated when you make changes to the body. That saves a lot of recompilation and makes changing the implementation much more painless. You will still have to recompile if you change the specification, but that's not something you should be doing very often.

2. You can "overload" subprograms (procedures/functions). You can have several subprograms with the same name, but with a different number of parameters, or different types.

3. You can have persistent variables throughout a session without storing anything in a database table. Packages can have variables and constants that are initialized when the package is first used within a session, and then they are available for the remainder of the session for all future references to anything within that package. That comes in very handy.

4. Speaking of initialization, being able to call a procedure automatically the first time a package is used within a session can also come in very handy.

5. You can take advantage of "encapsulation." In essence, you can hide the implementation details from users but still give them all the information they need to use the package. Since they aren't aware of the details, that means you can change them with minimal impact or risk. Packages also support private subprograms and variables which are available only to other subprograms within the package, and remain completely hidden and inaccessible to anything outside the package.

6. You may notice some performance improvement when using packages. When you first use a package, the entire package may be loaded into memory, meaning fewer disk I/Os as you use the related items within.