Anonymous | Login

Project:

News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ]

[ Issue History ] [ Print ]

ID

0004614

Type

Category

Severity

Reproducibility

Date Submitted

Last Update

defect

[Openbravo ERP] Y. DBSourceManager

minor

always

2008-08-12 19:15

2009-04-22 00:00

Reporter

pmagnin

View Status

public

Assigned To

marvintm

Priority

normal

Resolution

fixed

Fixed in Version

Status

closed

Fix in branch

pi

Fixed in SCM revision

Projection

none

ETA

none

Target Version

OS

Windows

Database

Oracle

Java version

OS Version

XP Pro

Database version

Standard Edition 10.0.2

Ant version

Product Version

SCM revision

Review Assigned To

Web browser

Modules

Core

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

No

Summary

0004614: ant export.database Issue

Description

The database table structure is not well exported when you define a field as nvarchar2(2000). You can not specify the size type, for instance nvarchar2(2000 BITE). In the XML file associated to the table you have a field defined as nvarchar2(4000).
I suppose it is interprated as 4000 CHAR, you have the Oracle issue bellow :
ORA-00910: longitud especificada demasiado larga para este tipo de dato

Steps To Reproduce

1) Table Creation
   ==============

CREATE TABLE I_TEST
(
  I_ERRORMSG NVARCHAR2(2000),
)
TABLESPACE USERS

2) Export database structure
   =========================
ant export.database

3) The XML file does not fit the database dictionary
   =================================================
<?xml version="1.0"?>
  <database name="TABLE I_TEST">
    <table name="I_TEST">
      <column name="I_ERRORMSG" primaryKey="false" required="false" type="NVARCHAR" size="4000" autoIncrement="false"/>
    </table>
  </database>

Tags

Relationships [ Relation Graph ] [ Dependency Graph ]

Notes
(0008572) pmagnin (reporter) 2008-08-18 10:15	Workaround: Use VARCHAR2(2000 BYTE) instead of NVARCHAR2(2000).

(0008777) pjuvara (reporter) 2008-08-29 09:48	Antonio has not been been able to reproduce this issue. He will ask additional information about this issue.

(0010560) marvintm (developer) 2008-11-24 12:48	The problem with the size most likely was related to the Oracle instance definition. The change from NVARCHAR2 to NVARCHAR was caused by dbsourcemanager. The two datatypes are functionally equivalent, and NVARCHAR is always used by dbsourcemanager, so this is normal.

Issue History
Date Modified	Username	Field	Change
2008-08-12 19:15	pmagnin	New Issue
2008-08-18 10:15	pmagnin	Note Added: 0008572
2008-08-29 09:48	pjuvara	Note Added: 0008777
2008-08-29 09:48	pjuvara	Assigned To	=> marvintm
2008-08-29 09:48	pjuvara	Status	new => feedback
2008-09-24 10:59	marvintm	Severity	critical => minor
2008-09-25 11:40	marvintm	Status	feedback => scheduled
2008-09-25 11:40	marvintm	fix_in_branch	=> trunk
2008-11-24 12:45	marvintm	Status	scheduled => acknowledged
2008-11-24 12:45	marvintm	Status	acknowledged => scheduled
2008-11-24 12:48	marvintm	Status	scheduled => resolved
2008-11-24 12:48	marvintm	Resolution	open => fixed
2008-11-24 12:48	marvintm	Note Added: 0010560
2008-12-18 12:38	jpabloae	Sticky Issue	No => Yes
2008-12-18 12:39	jpabloae	Sticky Issue	Yes => No
2008-12-18 12:39	jpabloae	Tag Attached: dbsm_migrate
2008-12-18 12:41	jpabloae	Project	@4@ => Openbravo ERP
2008-12-18 12:41	jpabloae	Category	=> Y. DBSourceManager
2009-04-21 11:07	psarobe	Status	resolved => closed
2009-04-22 00:00	anonymous	sf_bug_id	0 => 2777899

Copyright © 2000 - 2009 MantisBT Group