Changes

Jump to: navigation, search

PostgreSQL Adapter-nexj/schema-test

492 bytes added, 12:46, 13 December 2010
2- Modifying Syntax
:: 2- STORAGE ENGINE: In MySQL, the storage engine is set to a transactional safe engine such as [http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL#MySQL:InnoDB InnoDB], whereas PostgreSQL has a single built in engine. So, implementation of '''''<code> appendTableSuffix() </code>''''' in PostgreSQLManager.java was removed
:: 3- CHARACTER SET: In MySQL, the character set should be defined when creating a table. Whereas in PostgreSQL when a database is created, the character set is set to 'UTF8' by default.
:: 4- AUTO INCREMENT: [http://pointbeingPostgreSQL doesn't support 'auto_increment' as some other databases for a unique identifier column.net/weblog/2008/03/mysql * There are two ways around this, 1-versus-postgresql-addingTo create a 'sequence', 2-Use SERIAL, which is a macro around 'sequence'. * SERIAL is an-auto-increment-'integer' and a 'sequence, with the column-default to the sequences next value. * As of postgreSQL 7.3, to-make a serial column unique, it should be specified as a unique constraint or aprimary key. more info @ [[PostgreSQL_Adapter-tablenexj/Resources#Mapping_Data_Types.html2C_Metadata | PostgreSQL Resources]]
::
<source lang=java>
CREATE TABLE test.RangeTest(
id integer serial not null, s text null, bin bytea null,
n integer null, n1 smallint null, l bigint null, "DEC" decimal(10,5) null,
f double precision null, d double precision null, tm timestamp null, b boolean null,
constraint RangeTest_PK primary key(id)
);
// Using SERIAL is another way to work around 'sequence'//CREATE SEQUENCE test.RangeTest_id_seq;//ALTER TABLE test.RangeTest ALTER COLUMN id SET DEFAULT NEXTVAL('test.RangeTest_id_seq');
</source>
1
edit

Navigation menu