If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Data Access, Manipulation & Batch Languages > Delphi, C etc > Delphi+Oracle - Error ORA-01722

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-18-03, 09:51
Hodgskin Hodgskin is offline
Registered User
 
Join Date: Nov 2003
Location: Brazil
Posts: 1
Delphi+Oracle - Error ORA-01722

Hi, I'm trying to make delphi 6.0 talk to oracle. I'm using dbexpress to make a connection, then I'm using a SQLTable, a DataSetProvider and a ClientDataSet.

Everything appears to be working fine, but when I call the DataSet.ApplyUpdates, I get the error: "ORA-01722 - Invalid number type" ... does anyone knows what is the problem?? Or what I'm doin wrong???



Thanks a lot, Hodgskin.


ps.: I have only one numeric field on my table and is a integer declared as "number(8)" ...
Reply With Quote
  #2 (permalink)  
Old 11-24-03, 06:10
satish_ct satish_ct is offline
Registered User
 
Join Date: Nov 2003
Location: Bangalore, INDIA
Posts: 333
Thumbs up

Hi,

In a fully normalised database design, relationships between entities are modelled using primary and foreign keys. Where the relationship has a low cardinality and the tables are frequently joined, it is common to denormalise to some extent to reduce the number of lookups required.

Using a single column to hold multiple attributes is another matter. Relationships cannot properly be modelled in this way. To retrieve related data requires that relationships be built into the application logic and doing so defies the driving principle behind the relational model

There is a bigger drawback. It also introduces a dependency between columns and requires that predicates be applied in a predetermined order. Neither relational database theory or the SQL standard define the order in which predicates are applied.

By default Oracle does not guarantee the order in which predicates are evaluated. Oracle also tries to handle column conparisons between differently typed columns as best it can. The rules for this are in the SQL Language manual. This means that if you have designed your application so that it is possible to compare columns of different types and you do not enforce type conversion, it is possible to get errors such as this.
__________________
SATHISH .
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On