Difference between revisions of "PostgreSQL Adapter-nexj/schema-test"
(Created page with '==Working Inside Schema 'test'== : <code> CREATE TABLE test.xxx </code> :: data types are changed in <code> appendColumnType() </code> in ''PostgreSQLSchemaManager.java'' based …') |
(→Working Inside Schema 'test') |
||
Line 1: | Line 1: | ||
==Working Inside Schema 'test'== | ==Working Inside Schema 'test'== | ||
− | + | ===Initializing the sql | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
: When a connection is first established, this initial SQL statement should execute in MySQL, which is not the case for PostgreSQL, so it was commented out: | : When a connection is first established, this initial SQL statement should execute in MySQL, which is not the case for PostgreSQL, so it was commented out: | ||
:: | :: | ||
Line 43: | Line 32: | ||
)engine=innoDB; | )engine=innoDB; | ||
</source> | </source> | ||
+ | : <code> CREATE TABLE test.xxx </code> | ||
+ | :: data types are changed in <code> appendColumnType() </code> in ''PostgreSQLSchemaManager.java'' based on each jdbc type's equivalent in PostgreSQL. | ||
+ | :: The implementation in <code> crateTextTable </code> in file ''PostgreSQLSchemaManager.java'' is removed for now (base class's version is being called). | ||
+ | : <code>CREATE INDEX test.xxx </code> | ||
+ | : <code> CREATE Trigger test.xxx // if it's needed for PostgreSQL as well as MySQL</code> | ||
+ | |||
− | |||
{|class="collapsible collapsed" style="border-style:solid;border-width:thin;border-color:black" | {|class="collapsible collapsed" style="border-style:solid;border-width:thin;border-color:black" | ||
!align="left" style="background-color:SteelBlue; font-weight:bold;border-style:solid;border-width:thin;padding: 2px 2px 2px 2px;"| '''Files to Configure''' | !align="left" style="background-color:SteelBlue; font-weight:bold;border-style:solid;border-width:thin;padding: 2px 2px 2px 2px;"| '''Files to Configure''' |
Revision as of 10:33, 10 December 2010
Working Inside Schema 'test'
===Initializing the sql
- When a connection is first established, this initial SQL statement should execute in MySQL, which is not the case for PostgreSQL, so it was commented out:
/* MySQLAdapter.java */
public String getInitialSQL()
{
StringBuffer buf = new StringBuffer();
buf.append("set sql_mode = concat(@@sql_mode, ',ANSI_QUOTES')"); // allow using doublequote when quoting column names in "CREATE TABLE" statements
buf.append(";set optimizer_search_depth = 0"); // let DB automatically decide on how long it takes to examine plans, improves long planning sessions
buf.append(";set max_sort_length = ").append
(Math.max(MAX_VARCHAR_PRECISION, MAX_VARBINARY_PRECISION)); // set TEXT/BLOB minimum sorting length to be same as cutoff between varchar/text
return buf.toString();
}
- Also the same line should be commented out in postgresql_create.sql script, which is being used to create tables in the database 'test':
/* nexj/core/persistence/sql/etc/postgresql_create.sql */
set sql_mode = concat(@@sql_mode, ',ANSI_QUOTES');
- After activating the connection, the database is locked.
- In MySQL, the storage engine is set to a transactional safe engine such as InnoDB, whereas PostgreSQL has a single built in engine. So, changes needed to be done to this script:
create table test.Account(
id binary(16) not null, contactId binary(16) not null, account Type varchar(16) character set utf8 not null, funds double null,
constraint Account_PK primary key(id)
)engine=innoDB;
-
CREATE TABLE test.xxx
- data types are changed in
appendColumnType()
in PostgreSQLSchemaManager.java based on each jdbc type's equivalent in PostgreSQL. - The implementation in
crateTextTable
in file PostgreSQLSchemaManager.java is removed for now (base class's version is being called).
- data types are changed in
-
CREATE INDEX test.xxx
-
CREATE Trigger test.xxx // if it's needed for PostgreSQL as well as MySQL
Files to Configure |
---|
|