Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Diego Morales — — source: Informix-list mailing list archive (1991-1998)
You need good programmers on Baan. In our case, we work with Triton 3.1_a1
(previous version of Baan IV), and our custom programs work better than
native programs. It's very very important the construct of good selects
statements on Baan.
Here is a little example:
// This is a very bad select
select tiitm001.dsca
from tiitm001
where
tiitm001.item = :thing
selectdo
(...)
endselect
// This is a good select
select tiitm001.dsca
from tiitm001
where
tiitm001._index1 = {:thing}
selectdo
(...)
endselect
Also it's important to try to make the query's using index. If it means
the construct of news indexes, make them. They (your programmers) have to
try to don't use query's with 'inrange' in where clauses.
We found a great number of native programs with 'bads' selects statements.
I don't know how is built Baan IV... but I know Triton 3.1_a1 and the
native source it's easily improvable.
Otherwise, the porting doesn't work fine. It always select all the fields
of the table, even though you only select one of these fields (this reduce
a lot the performance of each query to the database). You can check it
with 'onstat -g ses <sess_id>' directly from Informix. This is the main
problem of porting level 1 for Informix. I hope level 2 will not do the
same error... but I think that this level it will only run with Baan IV (I
will have to settle for porting level 1).
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.