Subject | Re: [IBO] This could be a bug in IBO. |
---|---|
Author | Don Gollahon |
Post date | 2001-12-01T20:29:09Z |
I just tried it and it still creates them wrong. Here's a sample of the
EditSql that it made.
UPDATE EXCLUDEINFO SET
DAY_ID =:DAY_ID, /*PK*/
ID =:ID, /*PK*/
SRVC_TIME =:SRVC_TIME, /*PK*
WHERE
DAY_ID = :OLD_DAY_ID AND
ID = :OLD_ID AND
SRVC_TIME = :OLD_SRVC_TIME
And here is the InsertSql it created:
INSERT INTO EXCLUDEINFO(
DAY_ID, /*PK*/
ID, /*PK*/
SRVC_TIME, /*PK*)
VALUES (
:DAY_ID,
:ID,
:SRVC_TIME)
The sql statement that I use is simply:
select *
from excludeinfo
I know this is easily fixed and probably is from the fact that all fields
are key fields. But it still created it wrong so that is why I was
reporting it as a slight bug.
Thanks.
""Don Gollahon"" <dlgllhn@...> wrote in message
news:9ub050$ug1$1@......
EditSql that it made.
UPDATE EXCLUDEINFO SET
DAY_ID =:DAY_ID, /*PK*/
ID =:ID, /*PK*/
SRVC_TIME =:SRVC_TIME, /*PK*
WHERE
DAY_ID = :OLD_DAY_ID AND
ID = :OLD_ID AND
SRVC_TIME = :OLD_SRVC_TIME
And here is the InsertSql it created:
INSERT INTO EXCLUDEINFO(
DAY_ID, /*PK*/
ID, /*PK*/
SRVC_TIME, /*PK*)
VALUES (
:DAY_ID,
:ID,
:SRVC_TIME)
The sql statement that I use is simply:
select *
from excludeinfo
I know this is easily fixed and probably is from the fact that all fields
are key fields. But it still created it wrong so that is why I was
reporting it as a slight bug.
Thanks.
""Don Gollahon"" <dlgllhn@...> wrote in message
news:9ub050$ug1$1@......
> I recreated the whole database from scratch. This table had that problemcertain
> before I changed it, too. The table is part of a scheduler that I've been
> using. It coordinates data from two other tables, a member table which is
> the ID field, and an event table which is the Day_id and Srvc_time fields.
> People are randomly scheduled for several months at a time to cover
> events. The ExcludeInfo is a list of events that people cannot covereach
> because they are not available. The scheduler knows which to skip for
> person by this table. They are all keyed so I can quickly find them.button
> Remember, this was in Paradox before and certain things had to be in order
> to easily port it to IB. I plan on cleaning up the table structures in a
> later release.
>
> Anyway. I didn't have any keylinks setup for this table. I'll try adding
> them and see if it creates the updateSql correctly. It seems to work okay
> without them since I manually adjusted the slight errors the generate
> created.___________________________________________________________________________
>
> "Helen Borrie" <helebor@...> wrote in message
> news:4.2.0.58.20011202002422.02090ae0@......
> > At 11:44 PM 30-11-01 -0600, Don Gollahon wrote:
> >
> > Did you delete and rebuild your persistent field objects after changing
> the structure of the table? Delphi won't do this for you...
> >
> > Also double check that your KeyLinks are correct for the new structure.
> They should now be
> > ID
> > DAY_ID
> > SRVC_TIME
> >
> > (and I'm asking myself why you need all three columns in your primary
> key...)
> >
> > Helen
> >
> >
> > All for Open and Open for All
> > InterBase Developer Initiative � http://www.interbase2000.org
> > _______________________________________________________
> >
> >
> >
>
> > 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 Infohttp://docs.yahoo.com/info/terms/
> papers,
> > keyword-searchable FAQ, community code contributions and more !
> >
> > Your use of Yahoo! Groups is subject to
> >___________________________________________________________________________
> >
> >
>
>
>
>
>
> IB Objects - direct, complete, custom connectivity to Firebird orInterBase
> without the need for BDE, ODBC or any other layer.___________________________________________________________________________
>
> http://www.ibobjects.com - your IBO community resource for Tech Infopapers,
> keyword-searchable FAQ, community code contributions and more !
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>