![]() The main author of Sqlite, Dr D Richard Hipp, has since released Sqlite 3.0. Despite its simplicity, I found it effective and reliable. I actually made rather a lot of changes, adding basic transaction support and implementing a crude dataset based on a TList. An advantage for me was that I could easily see what the wrapper did and make my own amendments. Since I didn’t require databinding, I chose a wrapper that implemented very simple access to Sqlite – it was written by Ben Hochstrasser and amended by Pablo Pissanetzky. Although several of them were of good quality, I found myself running into bugs caused by the complexity of implementing Borland’s TDataset and related database components. There are various wrappers available for Delphi, and around 18 months ago I tried all the ones I could get my hands on. I had a Delphi 7 application using Sqlite 2.0. It is open source, free, cross-platform, fast, reliable, and well supported. ![]() SQLite is a small C library that has several advantages. Of course, it's not the "be-all, end-all" with respect to text processing and has lots of limitations, but it's a quite handy tool for this purpose.Most applications use a database, and there are many excellent database engines to choose from, both free and commercial. It can contain (and process with easy) quite a lot more. so one can't generalize and say that a memo is "like a footnote", as if it could contain no more than a few lines. The point, really, is that the ammount of text that can be loaded and treated with relative easy depends on lots of things which have little to do with TMemo itself: ammount of system memory, processor, disk throughput, etc. And yes, TMemo becomes extremely sluggish, but it can be done. I've used a TMemo (Delphi variant) to load and treat a 2,5 GiB text file (Project Gutenberg's ebooks metadata) on Windows XP and 7. started working on mwEdit, which later became SynEdit.īut when it became clear that the multiline edit was mainly used for text editors (the most notable MS Notepad), its capacity grew to close to the max the system allowed, and this has kept on growing through time. The 64Kb limit in Windows 16 bit (and some betas of Win95) is a well known PITA that's in fact, among other things, why Martin W. I don't usually repeat just what I read, and when I do so I tell it upfront not sure about 32 bit mode back then though. ![]() ![]() I also just tried that on my Windows 10 Tablet which is 32, that fails too even though it has 2G in it and nothing running when testing.īut I can get it to work on a Windows 7 PC which is 64 bit with 12G in it. I just experimented with a Vista PC, it won't let me get past 256k in size, although MS claims it should do 1G, don't believe all that you read. So different versions of windows have their limits. It has become a problem in windows trying to support large memos across versions So recently with windows 10 and maybe a little less, 64 bit I believe you can now do the 1/2 GB but the services of the memo becomes very slow in windows and its all about using the Long text over the short text options. Putting that aside, these controls still use the TStrings class to manage this in the LCL code and there comes a time when the Strringlist of the Early windows defaulted to 64k in size of a memo but you could change the size up to 256K then they upped it over time but there is still a limit on windows because it is a native controlįor other targets, the control is created in the widget set for the most part and thus can most like take the whole PC's content of memory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |