Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General Discussion » View Thread |
Messages 1 to 8 of 8 total |
Moving to EDB |
Wed, Jul 11 2007 12:56 PM | Permanent Link |
"Jerry Clancy" | We will release a new product in the very near future and the next few
months are the only time that I can safely make and test major changes to our products during the year. So, my questions are the following: 1) Is EDB ready for prime time? I suspect it is. I can live with minor bugs but not show-stoppers like infinite loops. 2) How easy (or hard) is the transition from DBISAM? 3) What is the impact on coding? I'm not an SQL person and save for textsearch there is none in my products. Can I continue to use my procedural code as is? Any input from those who have made this transition would be much appreciated. Jerry |
Wed, Jul 11 2007 9:20 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jerry,
<< 1) Is EDB ready for prime time? I suspect it is. I can live with minor bugs but not show-stoppers like infinite loops. >> Things are quieting down quite a bit, and the test bed that we have in place for EDB now is pretty substantial. So my answer would be yes, it is certainly read for prime time now. << 2) How easy (or hard) is the transition from DBISAM? >> It's not as easy as a DBISAM 3.x to 4.x upgrade, but you'll also find a lot about EDB to be similar to what is in DBISAM. The main differences are in the SQL-only aspects of EDB and the configuration and catalog files. Start here for more information: http://www.elevatesoft.com/edb1d7_dbisam_migration.htm << 3) What is the impact on coding? I'm not an SQL person and save for textsearch there is none in my products. Can I continue to use my procedural code as is? >> Yes, however any metadata changes such as creating tables, dropping tables, etc. must be done in SQL now: http://www.elevatesoft.com/edb1d7_tdbisamtable_component.htm -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Jul 12 2007 12:21 AM | Permanent Link |
"Jerry Clancy" | Tim,
Thanks for the response. I've perused the migration document a bit and it looks like most of the major changes will not affect me as, for example, I don't create or drop tables, etc. I see that Memo fields have become type CLOB but I assume I can do something like sString := FieldByName('CLOBField').AsString; Also noted that TEXTOCCURS has disappeared. Short of brute force (after the textsearch filter), how does one get a count of occurrences now? I'm impressed with the time that must have gone into the creation of the migration doc. Looks like you've done a great job with it. Jerry |
Thu, Jul 12 2007 2:41 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Jerry
If you use TEXTSEARCH a thing to beware of is that its replacement CONTAINS is ONLY available if the column you want to search in has a full text index created for it. Roy Lambert |
Thu, Jul 12 2007 4:11 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jerry,
<< Thanks for the response. I've perused the migration document a bit and it looks like most of the major changes will not affect me as, for example, I don't create or drop tables, etc. I see that Memo fields have become type CLOB but I assume I can do something like sString := FieldByName('CLOBField').AsString; >> Yep, the TDataSet architecture is all still the same. << Also noted that TEXTOCCURS has disappeared. Short of brute force (after thetextsearch filter), how does one get a count of occurrences now? >> Just so you know, TEXTOCCURS was always brute force anyways. The reason that it was removed was because the new text searching only operates on text-indexed columns, and there were some issues with using TEXTOCCURS in such a situation. It may make its way back in to the product at some point, but in a completely different manner. << I'm impressed with the time that must have gone into the creation of the migration doc. Looks like you've done a great job with it. >> Thanks. -- Tim Young Elevate Software www.elevatesoft.com |
Fri, Jul 13 2007 10:47 AM | Permanent Link |
"Jerry Clancy" | Thanks. I remember seeing that you get an error if it is not. I think in
DBISAM it just does a brute force search. BTW, one of your really old posts helped me a few weeks ago. Had a slow search and your post said make sure the field is marked for indexing and, sure enough, I had somehow inadvertently turned it off for the field I was searching. Jerry "Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message news:5E83009A-1889-44AC-9723-E9BBAB663679@news.elevatesoft.com... | Jerry | | | If you use TEXTSEARCH a thing to beware of is that its replacement CONTAINS is ONLY available if the column you want to search in has a full text index created for it. | | Roy Lambert | |
Fri, Jul 13 2007 10:50 AM | Permanent Link |
"Jerry Clancy" | "Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message news:32B05453-086F-4C85-8B58-B13CF90D1E12@news.elevatesoft.com... | Jerry, | << Also noted that TEXTOCCURS has disappeared. Short of brute force (after | thetextsearch filter), how does one get a count of occurrences now? >> | | Just so you know, TEXTOCCURS was always brute force anyways. The reason | that it was removed was because the new text searching only operates on | text-indexed columns, and there were some issues with using TEXTOCCURS in | such a situation. It may make its way back in to the product at some point, | but in a completely different manner. I actually always suspected that because even with the filter set it could be really slow. I now do my own checking for instances of the keywords after filtering. Jerry |
Fri, Jul 13 2007 4:41 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jerry,
<< BTW, one of your really old posts helped me a few weeks ago. Had a slow search and your post said make sure the field is marked for indexing and, sure enough, I had somehow inadvertently turned it off for the field I was searching. >> Cool. It's one of the reasons that I haven't archived any old posts yet from the newsgroups. However, the DBISAM newsgroups is getting a little big in size. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Friday, April 19, 2024 at 07:09 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |