Subject | Re: [IBO] possible problem IBO4.7.Beta 5 and IB_SQL |
---|---|
Author | Hans |
Post date | 2006-11-25T05:46:38Z |
The problem I'm trying to isolate is that on a join, the joined columns the
old way are read-only and now
they are not, causing a problem with Asta. Just cant quite put my finger on
it, but it does break all
formerly working Asta operation, with a trying to update a Read-Only columns
error message
old way are read-only and now
they are not, causing a problem with Asta. Just cant quite put my finger on
it, but it does break all
formerly working Asta operation, with a trying to update a Read-Only columns
error message
----- Original Message -----
From: "Jason Wharton" <supportlist@...>
To: <IBObjects@yahoogroups.com>
Sent: Friday, November 24, 2006 8:45 PM
Subject: RE: [IBO] possible problem IBO4.7.Beta 5 and IB_SQL
>I have made adjustments to the look and feel of IB_SQL.
>
> I don't see anything to get overly concerned about here.
>
> Please let me know if you feel I have missed something.
>
> I believe it is appropriate for stored procedure names to be treated as
> the
> relation name. It is possible to provide a relation alias name when using
> stored procedures and so it would be important to have that behavior also
> remain in keeping with things.
>
> Jason
>
>
>> -----Original Message-----
>> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
>> Behalf Of Hans
>> Sent: Friday, November 24, 2006 8:17 PM
>> To: IBObjects@yahoogroups.com
>> Subject: [IBO] possible problem IBO4.7.Beta 5 and IB_SQL
>>
>>
>> [IBO] possible problem IBO4.7.Beta 5 or/and IB_SQL
>>
>> ALTER PROCEDURE GETTICKETITEMS( MYTICKET_UNIQUENUM
>> INTEGER )
>> RETURNS ( TICKET_UNIQUENUM INTEGER
>> , TICKET_ENTRYNO INTEGER
>> , HOUSE_UNIQUENUM INTEGER
>> , PROD_NAME . VARCHAR(40)
>>
>> A select * from GETTICKETITEMS(75827)
>>
>> ========================================================
>>
>> Old IB_SQL on FB1.5.3 produces
>>
>> Fieldnames:
>> TICKET_UNIQUENUM
>> TICKET_ENTRYNO
>> HOUSE_UNIQUENUM
>> PROD_NAME
>>
>> Fields Field Type
>> TICKET_UNIQUENUM Integer
>> TICKET_ENTRYNO Integer
>> HOUSE_UNIQUENUM Integer
>> PROD_NAME VarText(40)
>>
>> ========================================================
>>
>>
>> New IB_SQL on FB2.0.0 produces
>> Fieldnames
>> GETTICKETITEMS.TICKET_UNIQUENUM
>> GETTICKETITEMS.TICKET_ENTRYNO
>> GETTICKETITEMS.HOUSE_UNIQUENUM
>> GETTICKETITEMS.PROD_NAME
>>
>> Fields
>> Field Type
>> GETTICKETITEMS.TICKET_UNIQUENUM (Integer)INTEGER
>> GETTICKETITEMS.TICKET_ENTRYNO (Integer)INTEGER
>> GETTICKETITEMS.HOUSE_UNIQUENUM (Integer)INTEGER
>> GETTICKETITEMS.PROD_NAME (VarText)VARCHAR(40)
>>
>> ========================================================
>>
>> New IB_SQL on FB1.5.3 produces
>> Fieldnames
>> TICKET_UNIQUENUM
>> TICKET_ENTRYNO
>> HOUSE_UNIQUENUM
>> PROD_NAME
>>
>> Fields
>> Field Type
>> GETTICKETITEMS.TICKET_UNIQUENUM (Integer)INTEGER
>> GETTICKETITEMS.TICKET_ENTRYNO (Integer)INTEGER
>> GETTICKETITEMS.HOUSE_UNIQUENUM (Integer)INTEGER
>> GETTICKETITEMS.PROD_NAME (VarText)VARCHAR(40)
>
>
>
> ___________________________________________________________________________
> IB Objects - direct, complete, custom connectivity to Firebird or
> InterBase
> without the need for BDE, ODBC or any other layer.
> ___________________________________________________________________________
> http://www.ibobjects.com - your IBO community resource for Tech Info
> papers,
> keyword-searchable FAQ, community code contributions and more !
> Yahoo! Groups Links
>
>
>