Fwd: EOModeler, INTEGER and Frontbase

After a bit of trail and error, I have discovered the exception is  
being raised because of the column name - not the data type - as  
POSITION is a apparently a reserved identifier for a string function  
in SQL 92. Double-quoting the column name in the SQL call fixes the  
exception.

I still don't understand why the data type is not matching EOModeler  
though. Interestingly, if i add a column to the Frontbase table using  
FBManager, and set it's data type to INTEGER, upon save it changes it  
to INT as well!

simon

> Hi All - Raw sql is not my usual territory so please forgive me if  
> this is a basic question, but here goes...
>
> We have been using a commerical reporting tool to generate reports  
> based on a Frontbase database. The reporting tool is receiving an  
> exception from Frontbase when it tries to call this:
>
> SELECT COUNT(POSITION) FROM URLMAP;
>
> I believe the reason is because the POSITION data type in Frontbase  
> is INT.
>
> However, the SQL being used to generate the table is:
>
> CREATE TABLE URLMAP(ACTUALDIR VARCHAR(100) NOT NULL,WEBPATH VARCHAR 
> (100),POSITION INTEGER);
>
> Why is Frontbase assigning the data type as "INT" and not "INTEGER" ?
>
> Any help appreciated.
>
> Thanks, Simon
>
>