Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 21 to 29 of 29 total |
Blob file re-use |
Thu, Feb 4 2010 10:04 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Matthew,
BTW, just to double-check on that DBISAM version #: We did have this bug: http://www.elevatesoft.com/incident?action=viewrep&category=dbisam&release=4.28&type=f&incident=3037 but it was fixed in 4.29. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Feb 4 2010 12:43 PM | Permanent Link |
(Matthew Jones) | As I posted just after my original post, I'm on 4.29 build 1.
IIRC I updated due to that report. /Matthew Jones/ |
Thu, Feb 18 2010 12:53 PM | Permanent Link |
(Matthew Jones) | Okay, just to keep all informed on this, I found a bug in my code which did the
purge. The purge was written to delete records older than a given number of minutes. However, it was originally done for a given number of days, but that obviously became an issue so I changed it. //Original: szPurgeDate := Engine.QuotedSQLStr( Engine.DateToAnsiStr(IncDay(Date, -nMinsToKeep), true)); // Modified for minutes, not days: szPurgeDate := Engine.QuotedSQLStr( Engine.DateToAnsiStr(IncMinute(Date, -nMinsToKeep), true)); // what it should have been changed to: szPurgeDate := Engine.QuotedSQLStr( Engine.DateTimeToAnsiStr(IncMinute(Now, -nMinsToKeep), true)); So, my bad! I should have looked at the surrounding code when doing the change. /Matthew Jones/ |
Thu, Feb 18 2010 1:07 PM | Permanent Link |
"Eduardo [HPro]" | Matthew
> So, my bad! I should have looked at the surrounding code when doing the > change. It happens. The most important thing is your feed-back about this issue. Eduardo |
Thu, Feb 18 2010 5:29 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Matthew,
<< Okay, just to keep all informed on this, I found a bug in my code which did the purge. The purge was written to delete records older than a given number of minutes. However, it was originally done for a given number of days, but that obviously became an issue so I changed it. >> Ah, cool, thanks for the update. So, basically the application was allowing records to accumulate for several days instead of several minutes ? -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Feb 22 2010 9:22 AM | Permanent Link |
(Matthew Jones) | > So, basically the application was allowing
> records to accumulate for several days instead of several minutes ? Yes. I'm now looking at a related issue where a server is having problems storing a 77Mb file in the blob! I've modified the code to have a blob size of 61440 to reduce the number of blobs it needs (7,590 approx at the old 10240 size). I find that setting the blob size in the alter table of DbSys to what it says is the max causes it to fail, and then corrupt the database when I click No. But I don't care as it works in code. /Matthew Jones/ |
Tue, Feb 23 2010 4:58 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Matthew,
<< I'm now looking at a related issue where a server is having problems storing a 77Mb file in the blob! I've modified the code to have a blob size of 61440 to reduce the number of blobs it needs (7,590 approx at the old 10240 size). I find that setting the blob size in the alter table of DbSys to what it says is the max causes it to fail, and then corrupt the database when I click No. But I don't care as it works in code. >> DBSYS should behave just like your code - it uses the same core DBISAM code. What block size are you trying to use when it fails, and what error message are you seeing ? -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Feb 24 2010 7:23 AM | Permanent Link |
(Matthew Jones) | > DBSYS should behave just like your code - it uses the same core
> DBISAM code. What block size are you trying to use when it fails, > and what error message are you seeing ? I typed in the number DbSys told me was the largest I could use. The message was a generic "something went wrong, yes, no, cancel or something else" response. I clicked No. I'll see if I can repeat it when I get a moment. /Matthew Jones/ |
Thu, Feb 25 2010 7:58 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Matthew,
<< I typed in the number DbSys told me was the largest I could use. The message was a generic "something went wrong, yes, no, cancel or something else" response. I clicked No. I'll see if I can repeat it when I get a moment. >> I'll check it out. Thanks, -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 3 of 3 | |
Jump to Page: 1 2 3 |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |