more OracleEdmWizard.exe bugs
Posted: Wed 23 Jan 2008 08:36
using oracle 9.2i.
My Schema contains table named "SystemRoles". the name is with quotes so it'll maintain small and capital letters, more convenient for reading.
CREATE TABLE "SHIPS"."SystemRoles"
(
"RoleId" NUMBER(2) NOT NULL ENABLE,
"RoleName" NVARCHAR2(20) NOT NULL ENABLE,
"RecordVersion" NUMBER(4) NOT NULL ENABLE,
"RecordUpdate" DATE NOT NULL ENABLE,
"RecordUpdateBy" VARCHAR2(20 CHAR) NOT NULL ENABLE,
PRIMARY KEY ("RoleId")
)
It seems your tool does not support tables and colum names with quotes for making them nicely read.
It works though when I change to
CREATE TABLE SHIPS.SYSTEMROLES
(
ROLEID NUMBER NOT NULL ENABLE,
ROLENAME VARCHAR2(20 BYTE) NOT NULL ENABLE,
RECORDVERSION NUMBER(4,0) NOT NULL ENABLE,
RECORDUPDATE DATE NOT NULL ENABLE,
RECORDUPDATEBY VARCHAR2(20 BYTE) NOT NULL ENABLE,
PRIMARY KEY (ROLEID)
)
But that would create ugly named objects in c#. The camel case notation is important for my readability.
The tool does not support mapping TIMESTAMP column, and it should not be a problem to map it as DateTime in .NET.
It also seems not to support NVARCHAR2 ?
Take this table definition for example:
CREATE TABLE SHIPS.SYSTEMUSERS
( USERID NUMBER NOT NULL ENABLE,
USERNAME VARCHAR2(20 BYTE) NOT NULL ENABLE,
APPROVED NUMBER(1,0) NOT NULL ENABLE,
RECORDVERSION NUMBER(4,0) NOT NULL ENABLE,
RECORDUPDATE DATE NOT NULL ENABLE,
RECORDUPDATEBY VARCHAR2(20 BYTE) NOT NULL ENABLE,
PRIMARY KEY (USERID)
)
I cannot understand what is wrong about it .. however get the same exception.
Those tables even do not have foreign keys.
My Schema contains table named "SystemRoles". the name is with quotes so it'll maintain small and capital letters, more convenient for reading.
CREATE TABLE "SHIPS"."SystemRoles"
(
"RoleId" NUMBER(2) NOT NULL ENABLE,
"RoleName" NVARCHAR2(20) NOT NULL ENABLE,
"RecordVersion" NUMBER(4) NOT NULL ENABLE,
"RecordUpdate" DATE NOT NULL ENABLE,
"RecordUpdateBy" VARCHAR2(20 CHAR) NOT NULL ENABLE,
PRIMARY KEY ("RoleId")
)
It seems your tool does not support tables and colum names with quotes for making them nicely read.
It works though when I change to
CREATE TABLE SHIPS.SYSTEMROLES
(
ROLEID NUMBER NOT NULL ENABLE,
ROLENAME VARCHAR2(20 BYTE) NOT NULL ENABLE,
RECORDVERSION NUMBER(4,0) NOT NULL ENABLE,
RECORDUPDATE DATE NOT NULL ENABLE,
RECORDUPDATEBY VARCHAR2(20 BYTE) NOT NULL ENABLE,
PRIMARY KEY (ROLEID)
)
But that would create ugly named objects in c#. The camel case notation is important for my readability.
The tool does not support mapping TIMESTAMP column, and it should not be a problem to map it as DateTime in .NET.
It also seems not to support NVARCHAR2 ?
Take this table definition for example:
CREATE TABLE SHIPS.SYSTEMUSERS
( USERID NUMBER NOT NULL ENABLE,
USERNAME VARCHAR2(20 BYTE) NOT NULL ENABLE,
APPROVED NUMBER(1,0) NOT NULL ENABLE,
RECORDVERSION NUMBER(4,0) NOT NULL ENABLE,
RECORDUPDATE DATE NOT NULL ENABLE,
RECORDUPDATEBY VARCHAR2(20 BYTE) NOT NULL ENABLE,
PRIMARY KEY (USERID)
)
I cannot understand what is wrong about it .. however get the same exception.
Those tables even do not have foreign keys.