Javascript validation for Valid Website URL


function isValidURL(url){
var RegExp = /^(([\w]+:)?\/\/)?(([\d\w]|%[a-fA-f\d]{2,2})+(:([\d\w]|%[a-fA-f\d]{2,2})+)?@)?([\d\w][-\d\w]{0,253}[\d\w]\.)+[\w]{2,4}(:[\d]+)?(\/([-+_~.\d\w]|%[a-fA-f\d]{2,2})*)*(\?(&?([-+_~.\d\w]|%[a-fA-f\d]{2,2})=?)*)?(#([-+_~.\d\w]|%[a-fA-f\d]{2,2})*)?$/;
if(RegExp.test(url)){
return true;
}else{
return false;
}
}


Ayurvedic Herbal Tips – use of ayurved – about ayurved and herbal information


Ayurvedicherbaltips.com  contains lots of material related to ayurvedic trees, plans and use of ayurvedic medicines.

Here in Ayurvedic Herbal Tips you can information about 
Aamla – Aamalaki, Dhatri

Galo – Guduchi, Amrita
Satavari – Shatavari, Shatamuli
Aashandha – Ashvagandha
Tulsi – Tulsi, Sursa, Brinda
Rantulsi – Rantulsi, Vriddhatulsi
Ardusi – Vasaka
Kuvar – Grih kumari
Brahmi – Madukaparni
Gokhru – Gokshura
Nagod – Nirgundi
Aghedo – Apamarga
Bhoy Ambli – Bhumyamalaki, Bhoodharti
Bhoy Ringani – Kantakari
Garmalo – Aaragvadha
Ashok – Ashoka
Kanchnar – Kanchnar
Sargavo – Shobhanjana, shigru
Kharkhodi, Dodi – Jivanti



Garani, Koyal – Aparajita, Visnukranta
Shankhavali – Shankhpushpi
Fudino – Pudina
Indrajav, Kado – Svetakutaja
Dhaturo – Dhatur
Aankado – Arka
Paras pippado – Parisha
Pili karen – Ashvaha
Barmasi – Sadappuspi
Bhangro – Bhringaraja
Lilu Kariyatu – Kalamegh, Bhunimba, Kirata
Darudi – Swarna ksiri
Kamal – Kamal
Kiddamari – Dhumrapatra
Mahendi – Madyantica
Chandan – Chandana
Bavad – Babbula
Khat Khatumbo – Amlaparni
Kuvadio – Chakramarda
Jasud – Japa
Gadariyu – Arishta
Aavad – Aavartaki, Arbur
Ingoriyo – Ingudi
Dudhiyo Hemkand – Hemakand
Khajvani – Vrischikali
Marvo – Munjariki, vedhi Marubak
Pipalo – Aswattha
Karanja – Karanjo
Satodi – Punarnva
Anantmool – Ananta
Limdo – Nimba
Vad – Vata
Khakhro – Palas
Arni – Agnimanthan
Arjunsadad – Arjun

and many more information at www.ayurvedicherbaltips.com

List your business / classified ads / buy offers / sell offers for free

Business Listing India

Business Listing India provides free services as follows,
Submit your business for free,
submit your classified ads for free,
submit your buy/sell offers for free,
The business directory,
Free Directory List,
Free Classified Ads,
Classifieds,
Buy Offer,
Sell Offer,
Free List Classified Ads,
Generate unlimited pages of your business,
Business listing india will help to rank your business in search engine.

For more information visit <a href=”http://www.businesslistingindia.com/”> Business Listing India </a>

Email : info@businesslistingindia.com

http://www.businesslistingindia.com/

Best Magento Site List

Below are the list of top and best magento sites. You can refer and share below sites.

http://inchoo.net/category/ecommerce/magento

http://yoast.com/

http://blog.velite.de/
http://www.mxperts.de/
http://blog.chapagain.com.np/
http://redbeardtechnologies.wordpress.com/category/magento/
http://snippi.net/
http://www.stunicholls.com/ http://www.inacode.com
http://www.patternhead.com/found-freebies/21-free-magento-themes-for-your-e-commerce-store
http://visionwidget.com/inspiration/web/374-free-magento-extensions.html
http://www.casualcommerce.com/
http://magentoexpert.blogspot.com/
http://blog.magentomagik.com/
http://www.exploremagento.com/
http://www.maglance.com/

http://www.magentocommerce.com/

http://www.magentocommerce.com/wiki/
http://www.magentocommerce.com/boards
http://asia-connect.com.vn/

Search Engine Blogs and Resources

Resources for Search Engine Optimization
SearchEngineWatch http://searchenginewatch.com/
SEO Book http://www.seobook.com/
Matt Cutts’ blog http://www.mattcutts.com/blog/
Search Engine Roundtable http://www.seroundtable.com/
ThreadWatch http://www.threadwatch.org/
SEO Black Hat http://seoblackhat.com/
Google Blog http://googleblog.blogspot.com/
Google Blogoscoped http://blog.outer-court.com/
John Battelle http://battellemedia.com/
Copyblogger http://www.copyblogger.com/
Yahoo! Search Blog http://www.ysearchblog.com/
Carsten Cumbrowski http://www.cumbrowski.com/
SEO Egghead http://www.seoegghead.com/
The Above Resources may be useful to you.

Best Practices for Title Tags



How to Make the Best Title Tag Possible:

  1. Brand your traffic
    Use the title of your site or brand at the beginning or end of every title tag to help searchers know where they’re going and to increase return visits. If you’re struggling to find justification for this component, think of all the ad studies showing that consumers are willing to pay more for a “brand name” product than an off-brand or store brand item of the same type – apply this logic to the SERPs and you’ll find that users will go further down the rankings to click on a “trusted” brand.
  2. Limit length to 65 characters (including spaces) or less
    There’s no reason to cut off the last word and have it replaced with a “…” Note that the engines have fluctuated recently and Google, in particular, is now supporting up to 70 characters in some cases.
  3. Incorporate keyword phrases
    This one may seem obvious, but it’s critical that whatever your keyword research shows as being the most valuable for capturing searches gets prominently included in your title tag. It doesn’t have to be the first words, but it should be the semantic and logical center of attention.
  4. Target longer phrases if they’re relevant
    When choosing what keywords to include in a title tag, I often like to use as many as are completely relevant to the page at hand, while remaining accurate and descriptive. Thus, it can be much more valuable to have a title tag like “SkiDudes | Downhill Skiing Equipment & Accessories” rather than simply “SkiDudes | Skiing Equipment” – including those additional terms that are both relevant to the page and receive significant search traffic can bolster your page’s value. However, if you have a separate landing page for “Skiing accessories” than for “equipment,” then you shouldn’t include one term in the other’s title – you’ll be cannibalizing your rankings by forcing the engines to choose which page on your site is more relevant.
  5. Use a divider
    When splitting up the brand from the descriptive, I like to use the “|” symbol (aka the pipe bar). Others choose the arrow “>” or hyphen “-” and both work well. At times, however, I’ve found it useful to use the arrow or hyphen inside a title tag, as with a title like “SEOmoz | Articles > Keyword Research – A Beginner’s Guide” hence my love of the pipe bar.
  6. Focus on clickthrough & conversion rates


    The title tag is exceptionally similar to the title you might write for paid search ads, only it’s harder to measure and improve because the stats aren’t provided for you as easily. However, if you’ve got a market that is relatively stable in search volume week-to-week, you can do some testing with your title tags and improve the clickthrough. Watch your analytics and, if it makes sense, buy search ads on the page as well – even if it’s just for a week or two, it can make a huge difference in the long run. A word of warning, though – be wary that you don’t focus entirely on CTR. Remember to continue measuring conversion rates.
  7. Target searcher intent
    When you’re writing titles for web pages, keep in mind the search terms your audience employed to reach your site. If the intent is browsing or research-based, a more descriptive title tag is appropriate. If you’re reasonably sure the intent is a purchase, download or other action, make it clear in your title that this function can be performed at your site, i.e. “SkiDudes | View Snowboard Sizing Chart” or “SkiDudes | Buy Discount Snoqualmie Pass Lift Tickets
  8. Be consistent
    Once you’ve determined a good formula for your pages in a given section or area of your site, stick to that regimen – you’ll find that as you become a trusted and successful “brand” in the SERPs, users will seek out your pages on a subject area and have expectations that you’ll want to fulfill.
  9. Repeat in the headline
    Re-using the title tag of each page as the H1 header tag can be valuable from both a keyword targeting standpoint and a user experience improvement. Users who go to a page from the SERPs will have the expectation of finding the title they clicked – deliver and you’ve fulfilled that obligation. Users will be more likely to stay on a page they’re reasonably certain fits their intended goal or query.

Types of SQL Statements Supported by MySQL

Selecting, Creating, Dropping, and Altering Databases

USE

CREATE DATABASE

DROP DATABASE

ALTER DATABASE

Creating, Altering, and Dropping Tables and Indexes

CREATE TABLE

DROP TABLE

CREATE INDEX

DROP INDEX

ALTER TABLE

Getting Information About Databases and Tables

DESCRIBE

SHOW

Retrieving Information from Tables

SELECT

UNION

Performing Transactions

SET autocommit

START TRANSACTION

COMMIT

ROLLBACK

Modifying Information in Tables

DELETE

INSERT

LOAD DATA

REPLACE

UPDATE

Administrative Statements

FLUSH

GRANT

REVOKE

Stop Right Click on your page using Javascript

Hey.. Now you can stop Right Click on your page using Javascript.
You can Use the following javascript code to your page.

Example :

<html>
<title>No Right Click</title>

<script> var isNS = (navigator.appName == “Netscape”) ? 1 : 0; if(navigator.appName == “Netscape”) document.captureEvents(Event.MOUSEDOWN||Event.MOUSEUP); function mischandler(){ return false; } function mousehandler(e){ var myevent = (isNS) ? e : event; var eventbutton = (isNS) ? myevent.which : myevent.button; if((eventbutton==2)||(eventbutton==3)) return false; } document.oncontextmenu = mischandler; document.onmousedown = mousehandler; document.onmouseup = mousehandler; </script>
</head>

<body>

<H3> TRY TO RIGHT CLICK..THE PAGE IN WHICH YOU HAVE PLACED THE ABOVE CODE.
</body>
</html>

MySQL Naming Rules

Almost every SQL statement refers in some way to a database or its constituent elements. This section describes the syntax and case sensitivity rules for identifiers that refer to databases, tables, columns, indexes, and aliases.

Referring to Elements of Databases

When you use identifiers to refer to elements of databases, you are constrained by the characters you can use and the length that identifiers can be. The format of identifiers also depends on the context in which you use them. Another factor that affects naming rules is that the server can be configured to use different SQL modes.

  • Legal characters in identifiers. Unquoted identifiers can consist of any alphanumeric characters in the system default character set (utf8), plus the characters ‘_‘ and ‘$‘. Identifiers can start with any character that is legal in an identifier, including a digit. However, an identifier cannot consist entirely of digits because that would make it indistinguishable from a number. MySQL’s support for identifiers that begin with a number is somewhat unusual among database systems. If you use such an identifier, be particularly careful if it contains an ‘E‘ or ‘e‘ because those characters can lead to ambiguous expressions. For example, the expression 23e + 14 (with spaces surrounding the ‘+‘ sign) means column 23e plus the number 14, but what about 23e+14? Does it mean the same thing, or is it a number in scientific notation? You should also be careful about using identifiers such as 0x1020 that begin with 0x because they might be interpreted as hexadecimal constants.
  • Identifiers can be quoted (delimited) within backtick characters (‘´‘), which allows use of any character except backtick or a byte with value 0 or 255:

    CREATE TABLE ´my table´ (´my column´ INT);

    Quoting is useful when an identifier is an SQL keyword or contains spaces or other special characters. Quoting an identifier also allows it to be entirely numeric, something that is not true of unquoted identifiers. To include an identifier quote within a quoted identifier, double it.

    For database and table identifiers, there are two additional constraints, even for identifiers that are quoted. First, you cannot use the ‘.‘ character, because it is used as the separator character in qualified name notation of the forms db_name.tbl_name and db_name.tbl_name.col_name. Second, you cannot use the Unix or Windows pathname separator characters (‘/‘ or ‘\‘). The pathname separator is disallowed in database and table identifiers because databases are represented on disk by directories, and tables are represented on disk by at least one file. Consequently, these types of identifiers must contain only characters that are legal in directory names and filenames. The Unix pathname separator is disallowed on Windows (and vice versa) to make it easier to transfer databases and tables between servers running on different platforms. (Suppose that you were allowed to use a slash in a table name on Windows. That would make it impossible to move the table to Unix, because filenames on that platform cannot contain slashes.)

    Your operating system might impose additional constraints on database and table identifiers. See “Operating System Constraints on Database and Table Naming,” in Chapter 10, “The MySQL Data Directory.”

    Column and table aliases can be fairly arbitrary. You should quote an alias within identifier quoting characters if it is an SQL keyword, is entirely numeric, or contains spaces or other special characters. Column aliases also can be quoted with single quotes or double quotes.

  • Server SQL mode. If the ANSI_QUOTES SQL mode is enabled, you can quote identifiers with double quotes (although backticks still are allowable).
  • CREATE TABLE "my table" ("my column" INT);

    Note: Enabling ANSI_QUOTES has the additional effect that string literals must be written using single quotes. If you use double quotes, the server will interpret the value as an identifier, not as a string.

    Function names normally are not reserved and can be used as identifiers without quotes. However, if the IGNORE_SPACES SQL mode is enabled, function names become reserved and must be quoted if used as identifiers.

    For instructions on setting the SQL mode, see “The Server SQL Mode” later in this chapter.

  • Identifier length. Identifiers for databases, tables, columns, and indexes can be up to 64 characters long. Identifiers are stored using utf8 characters. (Before MySQL 4.1.5, the maximum identifier length is 64 bytes, not characters. Because utf8 characters take from one to three bytes each, the effective maximum identifier length is less than 64 characters if you use multi-byte characters.) Aliases can be up to 256 characters long.
  • Identifier qualifiers. Depending on context, an identifier might need to be qualified to make clear what it refers to. To refer to a database, just specify its name:
    • A fully qualified table name consists of a database identifier and a table identifier:
    • SHOW COLUMNS FROM db_name.tbl_name;
      SELECT * FROM db_name.tbl_name;
    • A table identifier by itself refers to a table in the default (current) database. If sampdb is the default database, the following statements are equivalent:
    • SELECT * FROM member;
      SELECT * FROM sampdb.member;
    • A name written as db_name.tbl_name.col_name is fully qualified.
    • A partially qualified name written as tbl_name.col_name refers to a column in the named table in the default database.
    • An unqualified name written simply as col_name refers to whatever table is indicated by the surrounding context. The following two queries use the same column names, but the context supplied by the FROM clause of each statement indicates which table to select the columns from:
    • SELECT last_name, first_name FROM president;
      SELECT last_name, first_name FROM members;
  • USE db_name;
    SHOW TABLES FROM db_name;

    To refer to a table, you have two choices:

    If no database has been selected, you cannot refer to a table without specifying a database qualifier because the server cannot tell which database the table belongs to.

    To refer to a column, there are three choices: fully qualified, partially qualified, and unqualified.

    It’s usually unnecessary to supply fully qualified names, although it’s always legal to do so if you like. If you select a database with a USE statement, that database becomes the default database and is implicit in every unqualified table reference. If you’re using a SELECT statement that refers to only one table, that table is implicit for every column reference in the statement. It’s necessary to qualify identifiers only when a table or database cannot be determined from context. For example, if a statement refers to tables from multiple databases, any table not in the default database must be referenced using the db_name.tbl_name form to let MySQL know which database contains the table. Similarly, if a query uses multiple tables and refers to a column name that is used in more than one table, it’s necessary to qualify the column identifier with a table identifier to make it clear which column you mean.

    If you use quotes when referring to a qualified name, quote individual parts of the name separately. For example:

    SELECT * FROM ´sampdb´.´member´ WHERE ´sampdb´.´member´.´member_id´ > 100;

    Do not quote the name as a whole. This statement is illegal:

    SELECT * FROM ´sampdb.member´ WHERE ´sampdb.member.member_id´ >

Case Sensitivity in SQL Statements

Case sensitivity rules in SQL statements vary for different parts of the statement, and also depend on what you are referring to and the operating system of the machine on which the server is running:

  • SQL keywords and function names. Keywords and function names are not case sensitive. They can be given in any lettercase. The following statements are equivalent:
  • SELECT NOW();
    select now();
    sElEcT nOw();
  • Database and table names. MySQL represents databases and tables using directories and files in the underlying filesystem on the server host. As a result, the default case sensitivity of database and table names depends on the way the operating system on that host treats filenames. Windows filenames are not case sensitive, so a server running on Windows does not treat database and table names as case sensitive. Servers running on Unix usually treat database and table names as case sensitive because Unix filenames are case sensitive. An exception is that names in HFS+ filesystems under Mac OS X are not case sensitive.
  • You should consider lettercase issues when you create databases and tables on a machine with case sensitive filenames if it is possible that you will someday move them to a machine where filenames are not case sensitive. Suppose that you create two tables named abc and ABC on a Unix server where those names are treated differently. You would have problems moving the tables to a Windows machine. abc and ABC would not be distinguishable there because names are not case sensitive. You would also have trouble replicating the tables from a Unix master server to a Windows slave server.

    One way to avoid having case sensitivity become an issue is to pick a given lettercase and always create databases and tables using names in that lettercase. Then case of names won’t be a problem if you move a database to a different server. I recommend using lowercase. This will help also if you are using InnoDB tables, because InnoDB stores database and table names internally in lowercase.


    To force databases and tables to be created with lowercase names even if not specified that way in CREATE statements, configure the server by setting the lower_case_table_names system variable. See “Operating System Constraints on Database and Table Naming,” in Chapter 10.

  • Column and index names. Column and index names are not case sensitive in MySQL. The following queries are equivalent:
  • SELECT name FROM student;
    SELECT NAME FROM student;
    SELECT nAmE FROM student;
  • Alias names. By default, table aliases are case sensitive. You can specify an alias in any lettercase (upper, lower, or mixed), but if you use it multiple times in a statement, you must use the same lettercase each time. If the lower_case_table_names variable is non-zero, table aliases are not case sensitive.
  • String values. Case sensitivity of a string value depends on whether it is a binary or non-binary string, and, for a non-binary string, on the collation of its character set. This is true for literal strings and the contents of string columns. For further information, see “String Values,” in Chapter 3, “Working with Data in MySQL.”

Regardless of whether a database or table name is case sensitive on your system, you must refer to it using the same lettercase throughout a given query. That is not true for SQL keywords, function names, or column and index names, all of which may be referred to in varying lettercase style throughout a query. However, the query will be more readable if you use a consistent lettercase rather than “ransom note” style (SelECt NamE FrOm …).