IMPORTANT NOTE: you might need to reboot your phone in order to see the new alarm tone

P.S.: I’ve got a Samsung Galaxy i7500 and that worked for me. However, it should work for every Android phone.

I hope this helps.

1. Open a new tab.

2. Type about:config in the address bar and hit the enter key.

3. Search for urlbar in the Filter text box.

4. Change browser.urlbar.matchOnlyTyped to true and browser.urlbar.maxRichResults to 1 or any number of results you want firefox to suggest.

I hope this helps.

Object not found!

The requested URL was not found on this server. If you entered the URL manually please check your spelling and try again.

This might be due to the fact that it tries the following URL:

http://127.0.0.1/mysql/

Try this one instead:

http://127.0.0.1/home/mysql/

If it works then you can work it out by adding the following line to the httpd.conf file of Apache (you can find it under the %EASYPHP_HOME%/apache/conf path, where %EASYPHP_HOME% is the home directory of your EasyPHP installation). Open the file with a text editor and look up the following string: Alias /home/mysql

You should find something similar to the following line:

Alias /home/mysql “C:/Program Files/EasyPHP 3.0/phpmyadmin”

Just add, to the next line, the following string:

Alias /mysql “C:/Program Files/EasyPHP 3.0/phpmyadmin”

Restart EasyPHP. Now try to open http://127.0.0.1/mysql/. It should work.

What's the output produced by the previous code? If you think it is the following one you're wrong:
-Testing-
-split-
-using-
-two-
-whitespace-
-characters-

The actual output is instead the following one:

-Testing-
-split-
-using-
-two-
--
-whitespace-
-characters-

Where in the hell did that empty string come out from? It comes out from the two whitespace characters that are between the word two and whitespace of the str string. If this is what you want OK. However, most of the time, you will want to discard that empty string from your resulting string array. You can obtain this result by using the \\s+ regex in place of \\s. Basically, the previuos code becomes:

It might happen that while running a Java application within the Eclipse environment you get an OutOfMemoryError due to the maximum amount of memory dedicated to the heap. You can fix it by increasing the minimum (-Xms parameter) and maximum (-Xmx parameter) heap size. You can do it in two different ways:

1. By editing your eclipse.ini file you find under your Eclipse installation directory. Within that file you should find two lines similar to the following ones:

-Xms40m
-Xmx512m

You might want to change them depending on your hardware. For example I changed them as follows:

-Xms256m
-Xmx1024m

It means: "start with an initial heap size of 256 MB and grow to a maximum of 1024MB, that is 1GB."

2. By editing the Run Configurations in Eclipse. To do this, right-click on the class you want to run (the one with the main method) and then select:

Run As -> Run Configurations

Click on the Arguments tab. In the VM Arguments box type:

-Xms256m -Xmx1024m

or whatever you prefer, depending on the hardware you possess.

IMPORTANT NOTE: It is strongly recommended that you make a backup copy of your eclipse.ini file before editing it in any way.

An example of class where you can use these Java names for encoding is the OutputStreamWriter class

Of course you can edit the value assigned to the -moz-border-radius  property to  change the radius of the corner.

If you are sure that the field used to join the tables does not include NULL values then the IN operator performs "generally" better than EXISTS. I say "generally" because this is not always the case. For example consider the following query:

The previous query is processed more or less as follows:

The subquery is evaluated and the duplicates removed from the result (DISTINCT).
Then it is joined to the outer table. Now lets analyze the same query using NOT EXISTS:

The previous query is processed more or less as follows:

This means that using NOT EXISTS always results in a full scan of the outer table whereas the query which uses NOT IN can exploit an index on table_a.cd_field.
In general NOT IN performs better when the result of the subquery is small and there's an index on the field used by the join. On the other hand, NOT EXISTS is to prefer when the subquery has many rows, the outer query is relatively small and there's an index on the field used to join the two tables. In this latter case the cost of removing duplicates (DISTINCT) could be greater than the cost of the full scan of the outer table.

Of course this is a very general guideline, you should always conduct some test using indexes and so on to figure out which method to use.

Now try the following query:

Does the previous query return any row? The answer is NO it doesn't, even if there is a value (2) in table_a.cd_field which is not present in table_b.cd_field.

I think this is because NOT IN internally uses the inequality operator.
You should never use the equality or inequality operators with NULL, but IS NULL and IS NOT NULL, respectively.
For this reason, in SQL, NULL is not equal to NULL.
If you don't believe me then try the following query:

It returns 0 rows.

So how can you work this out? Enter the EXISTS (and NOT EXISTS) operator.

Try the following query:

The previous query returns 1 row, that is what you would expect since there is a row in table_a with cd_field = 2 which is not present in table_b.cd_field.

From now on beware of using NOT IN and IN when NULL values are involved.