[vwnc] PostgreSQL data types

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] PostgreSQL data types

Mike Hales
I'm getting errors where VW Floats are underflowing the PostgreSQL  
real data type.  How have other people dealt with this, and should  
this be dealt with in the postgres driver, or in user code some how?  
I guess I could make all my columns use the double precision type, but  
this would waste some space.  Currently I only use that type mapped to  
VW Doubles.  Do I need to worry about Doubles underflowing or  
overflowing the postgres double precision type?  I am using the IEEEFP  
math parcel and object engine switch.  I am using the EXDI interface  
1.3 053 that comes with the vw 7.6 distribution.  PostgreSQL version  
is 8.2 running on Windows.

Thanks,

Mike
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] PostgreSQL data types

Bruce Badger
On 12/04/2008, Mike Hales <[hidden email]> wrote:

> I'm getting errors where VW Floats are underflowing the PostgreSQL
>  real data type.  How have other people dealt with this, and should
>  this be dealt with in the postgres driver, or in user code some how?
>  I guess I could make all my columns use the double precision type, but
>  this would waste some space.  Currently I only use that type mapped to
>  VW Doubles.  Do I need to worry about Doubles underflowing or
>  overflowing the postgres double precision type?  I am using the IEEEFP
>  math parcel and object engine switch.  I am using the EXDI interface
>  1.3 053 that comes with the vw 7.6 distribution.  PostgreSQL version
>  is 8.2 running on Windows.

Mike,

Have a look at the PostgreSQLEXDIFieldValue hierarchy and the
>>buildTranslationsFromPostgres method on the class side of
PostgreSQLEXDISession.  You might find that adding explicit support
for floats here would help.

Alternatively, or in addition, you could add a test to
PostgreSQLEXDITest which fails in a situation which demonstrates the
issue.

All the best,
    Bruce
--
Make the most of your skills - with OpenSkills
http://www.openskills.org/
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc