1
edit
Changes
Created page with '* Database : Relational database Management System[http://en.wikipedia.org/wiki/Relational_database_management_system ] : Indexes & Hints :: [http://odetocode.com/Articles/70.asp…'
* Database
: Relational database Management System[http://en.wikipedia.org/wiki/Relational_database_management_system ]
: Indexes & Hints
:: [http://odetocode.com/Articles/70.aspx Index]
:: Hints - Hints are options or strategies specified for enforcement by the SQL Server query processor on SELECT, INSERT, UPDATE, or DELETE statements. The hints override any execution plan the query optimizer might select for a query.
:: Query Hints - http://msdn.microsoft.com/en-us/library/ms181714.aspx
:: Index vs Index Hint http://www.doens.be/2010/10/index-vs-index-hint/
: Trigger - A trigger is a specification that the database should automatically execute a particular function whenever a certain type of operation is performed. Triggers can be defined to execute either before or after any INSERT, UPDATE, orDELETE operation, either once per modified row, or once per SQL statement. If a trigger event occurs, the trigger's function is called at the appropriate time to handle the event.[http://www.postgresql.org/docs/8.1/interactive/triggers.html]
:: [http://en.wikipedia.org/wiki/Database_trigger Wiki]
:: [http://ovir.icp.ac.ru/oracle/doc/server/doc/scn73/ch15.htm Oracle Server Manual]
:: [http://dev.mysql.com/doc/refman/5.0/en/triggers.html MySQL] - Syntax [http://dev.mysql.com/doc/refman/5.0/en/trigger-syntax.html]
:: [http://www.postgresql.org/docs/8.1/interactive/triggers.html PostgreSQL]- Syntax [http://www.postgresql.org/docs/8.1/interactive/sql-createtrigger.html]
: Stored Procedures
:: [http://ovir.icp.ac.ru/oracle/doc/server/doc/scn73/ch14.htm Oracle Server Manual]
: Transactions
:: [http://ovir.icp.ac.ru/oracle/doc/server/doc/scn73/ch12.htm#toc094 Oracle Server Manual]
* Persistence
# Eclipse Tutorial Videos on [http://eclipsetutorial.sourceforge.net/persistence.html Persistence]
# [http://xstream.codehaus.org/persistence-tutorial.html XML/Object Binding] and [http://code.google.com/p/xbird/wiki/XmlObjectBinding Object Persistence] = [http://xstream.codehaus.org/index.html XStream] + [http://code.google.com/p/xbird/ XBird] (XML database system]
# data persistence with [http://www.developer.com/xml/article.php/918111/Data-Persistence-and-Java-Data-Objects----JDO.htm JDO]
# java world [http://www.javaworld.com/javaworld/jw-03-2002/jw-0301-jdo.html jdo]
* JDBC
# JDBC @ http://en.wikipedia.org/wiki/JDBC
# Relational database Management System @ http://en.wikipedia.org/wiki/Relational_database_management_system
# JDBC Driver @ http://en.wikipedia.org/wiki/JDBC_driver
# Drivers table http://devapp.sun.com/product/jdbc/drivers
===PostgreSQL and MySQL===
* Postgre
: [http://www.postgresql.org/docs/9.0/static/index.html Tutorial]
: [http://www.postgresql.org/docs/7.1/static/jdbc-ext.html postgre connection]
: String literals and string functions in postgreSQL [http://www.postgresql.org/docs/current/static/functions-string.html]
* MySQL
: [http://dev.mysql.com/doc/refman/5.1/en/sql-syntax.html Syntax]
: [http://dev.mysql.com/doc/refman/5.0/en/tutorial.html Tutorial]
: [http://www.mysql.com/downloads/connector/j/ Mysql Connector]
*The current versions are MySQL 5.1 and PostgreSQL 8.4.
#PostgreSQL is a unified database server with a single storage engine. MySQL has two layers, an upper SQL layer and a set of storage engines. [http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL]
#MySQL began development with a focus on speed while PostgreSQL began development with a focus on features and standards. Thus, MySQL was often regarded as the faster of the two.
# Both PostgreSQL and MySQL support Not-Null, Unique, Primary Key and Foreign Key constraints. However MySQL silently ignores the CHECK constraint
#MySQL supports stored procedures, per se; PostgreSQL supports stored functions, which are in practice very similar.
# Trigger - Both PostgreSQL and MySQL support triggers. A PostgreSQL trigger can execute any user-defined function from any of its procedural languages, not just PL/pgsql.MySQL triggers are activated by SQL statements only. They are not activated by changes in tables made by APIs that do not transmit SQL statements to the MySQL Server; in particular, they are not activated by updates made using the NDB API. PostgreSQL has always been strict about making sure data is valid before allowing it into the database, and there is no way for a client to bypass those checks.
# DataTypes - PostgreSQL does not have an unsigned integer data type, but it has a much richer data type support in several aspects: standards compliance, the logically fundamental data type BOOLEAN, user-defined data types mechanism, built-in and contributed data types. PostgreSQL allows columns of a table to be defined as variable-length multidimensional arrays. Arrays of any built-in or user-defined base type, enum type, or composite type can be created. Arrays of domains are not yet supported. MySQL does not have network IP address data types that PostgreSQL has but does provide INET_ATON() and INET_NTOA() functions to convert IPv4 addresses to and from easily stored integers. Postgres does very good job supporting referential integrity, has transactions and rollbacks, foreign keys ON DELETE CASCADE and ON UPDATE CASCADE.
#Security - MySQL has exceptionally good fine-grained access control. You can GRANT and REVOKE whatever rights you want, based on user name, table name and client host name.
#Alter table - Postgres supports ALTER TABLE to some extent. You can ADD COLUMN, RENAME COLUMN and RENAME TABLE. MySQL has all options in ALTER TABLE - you can ADD column, DROP it, RENAME or CHANGE its type on the fly - very good feature for busy servers, when you don't want to lock the entire database to dump it, change definition and reload it back.
#Diagnostic Log - By default, PostgreSQL logs to stderr, meaning that it's highly installation specific where the dianostic information is put; on this author's system, the default ends up in /var/lib/pgsql/pgstartup.log. The default can be set to something more reasonable (such as syslog on unix, eventlog on Windows) by adjusting thelog_destination configuration parameter.
#Automatic key generation -
:PostgreSQL doesn't support the standard's IDENTITY attribute. PostgreSQL's best offering for a column with auto-generated values is to declare a column of 'type' SERIAL:
<source lang=SQL>
CREATE TABLE tablename (
tablename_id SERIAL,
...
)
</source>
:MySQL doesn't support the standard's IDENTITY attribute. As an alternative, an integer column may be assigned the non-standard AUTO_INCREMENT attribute:
<source lang=SQL>
CREATE TABLE tablename (
tablename_id INTEGER AUTO_INCREMENT PRIMARY KEY,
...
)
</source>
: Compare SQL Implemenations[http://troels.arvin.dk/db/rdbms/ ]
: Compare Postgre and MySQL [http://www-css.fnal.gov/dsg/external/freeware/pgsql-vs-mysql.html]
: Comparison based on Postgre website [http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007]
: Relational database Management System[http://en.wikipedia.org/wiki/Relational_database_management_system ]
: Indexes & Hints
:: [http://odetocode.com/Articles/70.aspx Index]
:: Hints - Hints are options or strategies specified for enforcement by the SQL Server query processor on SELECT, INSERT, UPDATE, or DELETE statements. The hints override any execution plan the query optimizer might select for a query.
:: Query Hints - http://msdn.microsoft.com/en-us/library/ms181714.aspx
:: Index vs Index Hint http://www.doens.be/2010/10/index-vs-index-hint/
: Trigger - A trigger is a specification that the database should automatically execute a particular function whenever a certain type of operation is performed. Triggers can be defined to execute either before or after any INSERT, UPDATE, orDELETE operation, either once per modified row, or once per SQL statement. If a trigger event occurs, the trigger's function is called at the appropriate time to handle the event.[http://www.postgresql.org/docs/8.1/interactive/triggers.html]
:: [http://en.wikipedia.org/wiki/Database_trigger Wiki]
:: [http://ovir.icp.ac.ru/oracle/doc/server/doc/scn73/ch15.htm Oracle Server Manual]
:: [http://dev.mysql.com/doc/refman/5.0/en/triggers.html MySQL] - Syntax [http://dev.mysql.com/doc/refman/5.0/en/trigger-syntax.html]
:: [http://www.postgresql.org/docs/8.1/interactive/triggers.html PostgreSQL]- Syntax [http://www.postgresql.org/docs/8.1/interactive/sql-createtrigger.html]
: Stored Procedures
:: [http://ovir.icp.ac.ru/oracle/doc/server/doc/scn73/ch14.htm Oracle Server Manual]
: Transactions
:: [http://ovir.icp.ac.ru/oracle/doc/server/doc/scn73/ch12.htm#toc094 Oracle Server Manual]
* Persistence
# Eclipse Tutorial Videos on [http://eclipsetutorial.sourceforge.net/persistence.html Persistence]
# [http://xstream.codehaus.org/persistence-tutorial.html XML/Object Binding] and [http://code.google.com/p/xbird/wiki/XmlObjectBinding Object Persistence] = [http://xstream.codehaus.org/index.html XStream] + [http://code.google.com/p/xbird/ XBird] (XML database system]
# data persistence with [http://www.developer.com/xml/article.php/918111/Data-Persistence-and-Java-Data-Objects----JDO.htm JDO]
# java world [http://www.javaworld.com/javaworld/jw-03-2002/jw-0301-jdo.html jdo]
* JDBC
# JDBC @ http://en.wikipedia.org/wiki/JDBC
# Relational database Management System @ http://en.wikipedia.org/wiki/Relational_database_management_system
# JDBC Driver @ http://en.wikipedia.org/wiki/JDBC_driver
# Drivers table http://devapp.sun.com/product/jdbc/drivers
===PostgreSQL and MySQL===
* Postgre
: [http://www.postgresql.org/docs/9.0/static/index.html Tutorial]
: [http://www.postgresql.org/docs/7.1/static/jdbc-ext.html postgre connection]
: String literals and string functions in postgreSQL [http://www.postgresql.org/docs/current/static/functions-string.html]
* MySQL
: [http://dev.mysql.com/doc/refman/5.1/en/sql-syntax.html Syntax]
: [http://dev.mysql.com/doc/refman/5.0/en/tutorial.html Tutorial]
: [http://www.mysql.com/downloads/connector/j/ Mysql Connector]
*The current versions are MySQL 5.1 and PostgreSQL 8.4.
#PostgreSQL is a unified database server with a single storage engine. MySQL has two layers, an upper SQL layer and a set of storage engines. [http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL]
#MySQL began development with a focus on speed while PostgreSQL began development with a focus on features and standards. Thus, MySQL was often regarded as the faster of the two.
# Both PostgreSQL and MySQL support Not-Null, Unique, Primary Key and Foreign Key constraints. However MySQL silently ignores the CHECK constraint
#MySQL supports stored procedures, per se; PostgreSQL supports stored functions, which are in practice very similar.
# Trigger - Both PostgreSQL and MySQL support triggers. A PostgreSQL trigger can execute any user-defined function from any of its procedural languages, not just PL/pgsql.MySQL triggers are activated by SQL statements only. They are not activated by changes in tables made by APIs that do not transmit SQL statements to the MySQL Server; in particular, they are not activated by updates made using the NDB API. PostgreSQL has always been strict about making sure data is valid before allowing it into the database, and there is no way for a client to bypass those checks.
# DataTypes - PostgreSQL does not have an unsigned integer data type, but it has a much richer data type support in several aspects: standards compliance, the logically fundamental data type BOOLEAN, user-defined data types mechanism, built-in and contributed data types. PostgreSQL allows columns of a table to be defined as variable-length multidimensional arrays. Arrays of any built-in or user-defined base type, enum type, or composite type can be created. Arrays of domains are not yet supported. MySQL does not have network IP address data types that PostgreSQL has but does provide INET_ATON() and INET_NTOA() functions to convert IPv4 addresses to and from easily stored integers. Postgres does very good job supporting referential integrity, has transactions and rollbacks, foreign keys ON DELETE CASCADE and ON UPDATE CASCADE.
#Security - MySQL has exceptionally good fine-grained access control. You can GRANT and REVOKE whatever rights you want, based on user name, table name and client host name.
#Alter table - Postgres supports ALTER TABLE to some extent. You can ADD COLUMN, RENAME COLUMN and RENAME TABLE. MySQL has all options in ALTER TABLE - you can ADD column, DROP it, RENAME or CHANGE its type on the fly - very good feature for busy servers, when you don't want to lock the entire database to dump it, change definition and reload it back.
#Diagnostic Log - By default, PostgreSQL logs to stderr, meaning that it's highly installation specific where the dianostic information is put; on this author's system, the default ends up in /var/lib/pgsql/pgstartup.log. The default can be set to something more reasonable (such as syslog on unix, eventlog on Windows) by adjusting thelog_destination configuration parameter.
#Automatic key generation -
:PostgreSQL doesn't support the standard's IDENTITY attribute. PostgreSQL's best offering for a column with auto-generated values is to declare a column of 'type' SERIAL:
<source lang=SQL>
CREATE TABLE tablename (
tablename_id SERIAL,
...
)
</source>
:MySQL doesn't support the standard's IDENTITY attribute. As an alternative, an integer column may be assigned the non-standard AUTO_INCREMENT attribute:
<source lang=SQL>
CREATE TABLE tablename (
tablename_id INTEGER AUTO_INCREMENT PRIMARY KEY,
...
)
</source>
: Compare SQL Implemenations[http://troels.arvin.dk/db/rdbms/ ]
: Compare Postgre and MySQL [http://www-css.fnal.gov/dsg/external/freeware/pgsql-vs-mysql.html]
: Comparison based on Postgre website [http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007]
