Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 10 of 39 total |
Implications for defaulting CLOBS to EmptyString |
Fri, Jun 20 2008 10:26 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
Just posted this to the extensions ng and I suddenly thought - what, if any, are the implications of setting CLOBS & BLOBS to emptystring rather than NULL? Does this mean that the files will use BLOBBLOCKSIZE (or whatever it is in ElevateDB) bytes for each record in the table? --------------------------------------------------------------------------------------------------------------------------- John From a post by Tim way back in January in response to me << That's the easy (decision not doing) one. I'm still working on what to do with integers, floats, blobs, clobs, dates, times and timestamps. >> <<Except for BLOBS and CLOBS, which work like strings in terms of NULLs, the other types work exactly the same as DBISAM, therefore you shouldn't have to do anything.>> So both our scripts need a bit more work Roy Lambert --------------------------------------------------------------------------------------------------------------------------- Roy Lambert |
Fri, Jun 20 2008 1:28 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Just posted this to the extensions ng and I suddenly thought - what, if any, are the implications of setting CLOBS & BLOBS to emptystring rather than NULL? Does this mean that the files will use BLOBBLOCKSIZE (or whatever it is in ElevateDB) bytes for each record in the table? >> Yes. -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Jun 21 2008 3:50 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
><< Just posted this to the extensions ng and I suddenly thought - what, if >any, are the implications of setting CLOBS & BLOBS to emptystring rather >than NULL? > > Does this mean that the files will use BLOBBLOCKSIZE (or whatever it is in >ElevateDB) bytes for each record in the table? >> > >Yes. OUCH! Roy Lambert |
Sat, Jun 21 2008 7:20 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< OUCH! >> Yes, well, the assumption was that someone wouldn't go to the trouble of populating every BLOB in the table with empty data. -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Jun 21 2008 10:27 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
You forgot someone who wants consistency in his testing without having to use two different tests each time and who took your words literally without testing out the behaviour of TDBMemo, expecting it to work the same as TDBEdit. It doesn't. Deleting the contents of a TDBMemo and posting results in a NULL, deleting the contents of a TDBEdit results in an emptystring which we all know by now isn't a NULL. To save me having to hurt my brain by ferreting around in DB is this as a result of your work on the problem I had with .Clear and .IsNull with storing tables in blobs a while back or Delphi's? Anyway I'm now tearing up approach number one to solving my NULL issue - didn't like it much anyway. Roy Lambert |
Sat, Jun 21 2008 11:12 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< To save me having to hurt my brain by ferreting around in DB is this as a result of your work on the problem I had with .Clear and .IsNull with storing tables in blobs a while back or Delphi's? >> Yes, that's the reason. However, I figured out a way to do both, so I'll log this as an incident report and make sure that it's fixed in 2.00 B3. -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Jun 21 2008 11:17 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
><< To save me having to hurt my brain by ferreting around in DB is this as a >result of your work on the problem I had with .Clear and .IsNull with >storing tables in blobs a while back or Delphi's? >> > >Yes, that's the reason. However, I figured out a way to do both, so I'll >log this as an incident report and make sure that it's fixed in 2.00 B3. What, he asks suspiciously, is the both that you have figured out a way to do. Roy Lambert |
Sat, Jun 21 2008 11:31 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< What, he asks suspiciously, is the both that you have figured out a way to do. >> Allow for a Clear=NULL and a Set to ''=NOT NULL. -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Jun 21 2008 12:05 PM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tim
>Allow for a Clear=NULL and a Set to ''=NOT NULL. Arrggghh Just when I thought things were going my way a bit. Roy Lambert |
Sat, Jun 21 2008 2:23 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< Just when I thought things were going my way a bit. >> Right is right. If someone modifies a BLOB column without using Clear, then the result should be that the column is not NULL. -- Tim Young Elevate Software www.elevatesoft.com |
Page 1 of 4 | Next Page » | |
Jump to Page: 1 2 3 4 |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |