View Single Post
  #19  
Old February 11th, 2009, 02:11 PM
ElDiabloConCaca's Avatar
ElDiabloConCaca ElDiabloConCaca is online now
Registered User
 
Join Date: Aug 2001
Location: San Antonio, Texas
Posts: 12,673
Thanks: 7
Thanked 388 Times in 370 Posts
ElDiabloConCaca is a glorious beacon of lightElDiabloConCaca is a glorious beacon of lightElDiabloConCaca is a glorious beacon of lightElDiabloConCaca is a glorious beacon of lightElDiabloConCaca is a glorious beacon of lightElDiabloConCaca is a glorious beacon of light
Yes, Jeff is correct.

I understand completely about "editorial decisions" and that the author, many times, does not have much control nor say about what goes in and what gets axed from an article due to length constraints and audiences and other factors. I realize that sometimes it is difficult to summarize a point of view and limit it to a certain number of words or sentences -- and when this does happen, sometimes the point trying to be made is "lost in translation." Some things just need lengthier explanations and cannot be explained accurately when they're limited by space. Perhaps some of the ideas and concepts expressed in the blog were misconstrued by myself due to this.

I do have experience with Access -- perhaps not as much as to go writing blog entries about it, but I do know it quite well. The points that I took issue with were concerned with the storage of certain datum (for example, "images") and the assumption that storage of a specific data type inherently causes or is a factor in database corruption. My experience says that this is impossible -- an integer is no more likely to corrupt a database than a floating-point value, and a BLOB is no more likely to corrupt a database than an image (which are basically the same thing, anyway). What can corrupt a database with the use of these data types is improper use of them -- unsafely writing, modifying or adding data to a database that could cause some or all of the data to be written incorrectly or incompletely. This is more user behavior, though, than the binary data itself causing the corruption, and I agree -- it happens more frequently with those data types (simply because writing integers is closer to being an atomic operation than writing a much larger data type; in some cases, binary image data).

At any rate, perhaps we can swing back to some middle ground here and have ourselves a nice conversation about the pros and cons of this or that. We all have our opinions here, and because of the fact that they're opinions, that means that neither you nor I are "right" or "wrong;" in fact, there is no "right" or "wrong" -- simply "this view" and "that." I love a good debate, as long as it stays friendly and does not venture too far into the personal realm (hell, check out our nice little ditty in the "Viruses on OS X thread" -- fun conversation!).

I welcome any knowledge I can leech off of you as I'm sure you do me. I mean, that's why we're here, right? "The more you know..." as they say, and I am a believer that knowledge of and familiarity with a subject breeds convenience.
__________________
Mac mini 2.0GHz 10.6.2 • 4GB • 320GB • Superdrive • 4 x 1TB USB 2.0 • LED Cinema Display
MacBook 2.0GHz Core 2 Duo - White 10.6.2 • 4GB • 250GB • CD-RW/DVD-ROM
iPhone 3G 8GB • iPod Touch 8GB • iPod Photo 60GB • iPod nano 1GB • AT&T U-Verse 18Mb/2Mb
http://www.jeffhoppe.com
Reply With Quote
The Following User Says Thank You to ElDiabloConCaca For This Useful Post:
CactusData (February 12th, 2009)