Subject | Re: 4.0 BETA |
---|---|
Author | chrisl@wi.rr.com |
Post date | 2001-01-03T19:04:34Z |
> Jason,difference other than improved performance and "fluidity" of the
>
> Well, if I have done my job right you shouldn't have any apparent
interface.
Wow, this all sounds to good to be true.
> If you are using the TIBOTable component it will simply do just asthe BDE did.
This interests me. I assumed (without ever investigating it further)
that the TIBOTable component was only there for backward
compatibility and its use would most likely result in a major
performance penalty like in IBX. Is this not also the case with IBO ?
The BDE/Paradox app that I am converting makes very heavy use of
TTable components and I have been converting everything over to
TIBOQuery and/or Native components. Would you recomend this strategy
or is TIBOTable usage an acceptable practice in the IBO community ?
Is there a noticable performance penalty or higher then normal memory
usage when using TIBOTable ?
> So far the only hang-up is that if you are using more than onecolumn InterBase doesn't seem to optimize if all that well. Ann
Harrison is onto the bug for it and hopefully the initial release of
Firebird will have it resolved.
What exactly do you mean by this. Are you talking about having more
then one field in the ORDER BY clause of the SELECT statement ?
> Hope this is what you were looking for.Exactly what I was looking for (and then some).
> E) Addition of various modules for full text search, serviceapplications, simple replication, PDOX to IB migration tools, and
possibly more.
Having written a program to convert 250 Paradox tables over to IB, I
would be interested in seeing your version (when it arrives). So far
this was probably the toughest part of the entire conversion. So many
valid field names in Paradox are now reserved words in IB. Field
names in Paradox like "TotalValue" look pretty nasty when they get
converted over to TOTALVALUE. I ended up converting it over to
TOTAL_VALUE so that I would have better read-ability in code. AutoInc
fields need to be converted over to generators with the appropriate
triggers and the list goes on.
Thanks for the status update,
Chris Landowski
Dynamic Software Solutions