close Warning: Can't synchronize with repository "(default)" (/var/svn/tolp does not appear to be a Subversion repository.). Look in the Trac log for more information.

Opened 19 years ago

Last modified 16 years ago

#349 assigned defect

Problems selecting integral values from oracle database.

Reported by: jimarin Owned by: Jorge
Priority: lowest Milestone:
Component: DataBase Version: head
Severity: blocker Keywords:
Cc: Christian Paz

Description

Hi,

I have a database which is served by Oracle 9i.

In sadd table SetInput there is a field defined as INTEGER (or NUMBER(38) in
Oracle terms) called orderf.

I have introduced a line in that table that goes:

CODE ORDERF INHERITANCE SETINPUTFATHER DESCRIPTION
========================================
Pub_Si 1 N NULL Publicity

If I do:

Set DBTable(
"SELECT orderf FROM CNOSETINPUT;"
);

I get a 0 !!!!!!!!

Whereas if I do the same query by any other means (sql plus, sqltools, ...)

I get the 1 !!!!!

This is so bad that no operations against the Oracle database can be trusted.

jima

PS.
This error is very easy to reproduce.
This error does not take long to reproduce.
We urge for this error to be solved in the least amount of time possible.

Change History (6)

comment:1 Changed 19 years ago by Víctor de Buen Remiro

Hello

This error is "very" imposible to reproduce if you don't have any Oracle server to
ask your query, and take an eternity in this case.

I think it's a problem with new numerical data types in ODBC that are not revisited
in our ODBC to TOL connection software, but I don't known anything about ODBC,
so I can't resolve it.

However, I get similar errors with MySQL and I skip the problem with by casting to
standard types as double, or simply by adding 0.0E0 to forze casting more easily.
I hope it will run in this way.

Best regards

comment:2 Changed 19 years ago by danirus

Hi,
In other case I can care about it. Please Jima, let me know.
Cheers.

comment:3 Changed 19 years ago by jimarin

Well,

I think we should not forget platforms like Windows and Oracle.

A bug can be impossible to reproduce, but not seriously for the reasons mentioned.

Just my oppinion.

jima

comment:4 Changed 18 years ago by danirus

Status: newassigned

comment:5 Changed 18 years ago by Christian Paz

Cc: Christian Paz added

I saw and reported this error sometime ago (Bug 329).

About that time Jorge was working to solve this bug. We avoided this bug by making this "trick", replace for example:

select numeric_field from table1

with

select numeric_field+0 from table1

This returns the correct value for numeric_field.

Another tip: when calling from tol-console this error does not occur, i.e. the correct value is returned.

comment:6 Changed 16 years ago by Víctor de Buen Remiro

Owner: changed from danirus to Jorge
Note: See TracTickets for help on using tickets.