Free nifty online utilities

http://ideone.com/
 An online compiler and debugging tool which allows to compile and run code online in more than 40 programming languages.

http://browsershots.org/
Browsershots makes screenshots of your web design in different operating systems and browsers.

http://rubular.com/
A handy way to test regular expressions as you write them.

http://jsfiddle.net/
A html,  css  , javascript play ground. Also supports many frameworks like jquery ,YUI , Prototype etc

http://www.wolframalpha.com/
It's a computational knowledge engine: it generates output by doing computations from its own internal knowledge base, instead of searching the web and returning links.

http://yuml.me/
Create and share simple UML diagrams in your blogs, wikis, forums, bug-trackers and emails.

http://pixlr.com/editor/
An online photo editor.

the Big-Oh

http://www.csse.monash.edu.au/~lloyd/tildeAlgDS/Math/

Sun Tech Days 2010

Sybase Stored procedures Chained , UnChained mode

The terms Chained , UnChained here refer to how the transactions are handled.
Chained mode [ the ANSI SQL standard ] - In this mode the BEGIN TRANSACTION is always implicitly called by the server when the client calls the server. the client has to explicitly call the COMMIT or ROLLBACK to end the transaction.
So in Chained mode there is only explicit call to close tx but no explicit begin tx.
when using JDBC-Chained mode - Connection.setAutoCommit(false)

UnChained Mode - [The Sybase way]-Here there has to be both explicit BEGIN TX and COMMIT/ROLLBACK TX to close it.
when using JDBC - Unchained mode - Connection.setAutoCommit(true):
This mode is the default in sybase.


When stored procs are created in sybase the adaptive Server tags all procedures with the transaction mode ("chained" or "unchained") of the session in which they are created.

This helps avoid problems associated with transactions that use one mode to invoke transactions that use the other mode. A stored procedure tagged as "chained" is not executable in sessions using unchained transaction mode, and vice versa.

Triggers are executable in any transaction mode. Since they are always called as part of a data modification statement, either they are part of a chained transaction (if the session uses chained mode) or they maintain their current transaction mode.

sp_procxmode - to display or change the transaction mode of stored procedures.

more here

Identity Gaps in Sybase

Strange issue I noticed with id column values in the db tables.
they seem to take huge leaps suddenly!
sybase manual
more info here

DISTRICT 9

Finally got to watch this movie.I must say this is one of the best movies i have ever seen .With its clever faux documentary style, this is the most imaginative science-fiction movie to come along in years.It did remind me a bit of starship troopers but this one was much better.This is one alien movie where i see aliens running scared of humans.It has enough action , emotion that keeps you intrigued throughout till end.
The end of movie seemed sad to me and ended with some obvious questions.
All in all it was a really good movie.

Sybase interacive sql error

Just installed sybase 15.0.3 on 64 bit linux server successfully.Then tried to peek in my db using interactive sql but it just doesnt launch.It complains about some missing library.
"Interactive SQL could not load the "SQLAnywhere" plugin.
Its "saip11.jar" file has moved or has been deleted. You
will not ..."

The same error message is repeated for UltraLite and
GenericODBC and then I get a message saying:

"Interactive SQL cannot start because it is not installed
correctly. No database plugins has been registered. To fix
this problem you should reinstall the program."

After bit of searching i finally found the cause of the problem.
I had installed ase as using a wrong user login.

Under normal circumstance, the DBISQL registry file ($HOME/dbisql.rep)
should be correctly created by the installer. If for some reason the
file does not exist or if it's corrupted, the error messages mentioned
are raised (due to the fact that DBISQL assumes an ASA installation when
there is no registry).

To register ASEIsqlPlugin with DBISQL, first rename the
dbisql.rep file if it exists (just to be safe). Then, either re-run the
installer and install DBISQL again, or manually execute the following
command, assuming SYBROOT and SYBASE_JRE6 env variables are properly
defined:

$SYBROOT/DBISQL/bin/dbisql -Xregister aseisqlplugin11 "Adaptive Server
Enterprise" com.sybase.aseisqlplugin.ASEISQLPlugin
"$SYBROOT/shared/lib/jconn3.jar:$SYBROOT/DBISQL/lib/aseisqlplugin.jar:$SYBROOT/DBISQL/lib/jodbc.jar:$SYBROOT/DBISQL/lib/xml4j.jar:$SYBROOT/DBISQL/lib/planviewer.jar:$SYBROOT/DBISQL/lib/dsparser.jar:$SYBROOT/DBISQL/lib/asa.jar:$SYBROOT/DBISQL/lib/uaf-client.jar:$SYBROOT/DBISQL/lib/jini-core.jar:$SYBROOT/DBISQL/lib/jini-ext.jar:$SYBROOT/DBISQL/lib/jmxremote.jar:$SYBROOT/DBISQL/lib/jmxri.jar:$SYBROOT/DBISQL/lib/commons-logging.jar:$SYBROOT/DBISQL/lib/log4j-1.2.6.jar"

credits to Neal from sybase team for the explaination.

it never ends

Deleted everythg from v1.0 and starting now with v1.1