>avoided at all costs...
That reads anti-BLOB to me. But reardless, I'm just saying its not as
clear cut as that. There are legit reasons to storing large objects in
databases.
I also forgot another benefit, full-text searching.
-Adam
----- Original Message -----
From: Robertson-Ravo, Neil (RX) <[EMAIL PROTECTED]>
Date: Tue, 21 Sep 2004 16:15:48 +0100
Subject: RE: BLOB
To: CF-Talk <[EMAIL PROTECTED]>
Not at all, I am not anti-BLOB...just storing file objects etc is not
good....What if your DB is taken down.....?
_____
From: Adrocknaphobia [mailto:[EMAIL PROTECTED]
Sent: 21 September 2004 16:10
To: CF-Talk
Subject: Re: BLOB
Clustering and data integrity to name a couple reasons. If I have say
6 clusters worldwide supporting my application. A record in an
application can have multiple files associated with it. I can
piggy-back the database replication to move the files rather than
create and/or use a seperate system for replication.
Now I don't endorse putting every little thing into a database, and I
don't recommend it should be used as the primary storage. I belive it
was Jim Davis who wrote about a hybrid solution between database and
file-system. In the application I mentioned above, the files are
replicated across all the databases and CF pulls down new and/or
updated versions to store in file system. The application uses the
file-system for primary storage and retrival.
As for bloating the database size, it's pretty insignificant in the
grand scheme of things. (Of course I recommend you cap file sizes
regardless) Plus we now have the ability to perform a full database
backup without having to run backups on the file-system. At any point,
the database and source can be deployed as fully operational version,
without losing the files associated with the data.
I'm sorry if I was a bit blunt before, but like clockwork, if anyone
asks anything about BLOBs on this list, there is the immediate
criticism of "You shouldn't do that", rather than offering assitance.
-Adam
----- Original Message -----
From: Robertson-Ravo, Neil (RX) <[EMAIL PROTECTED]>
Date: Tue, 21 Sep 2004 15:42:06 +0100
Subject: RE: BLOB
To: CF-Talk <[EMAIL PROTECTED]>
Well yes and no, it's not just my opinion its also good SQL practice,
Storing data in BLOB's and CLOB's is not good full stop. It leads to
overgrown database systems and unnecessary storage of binary data. You have
to see it from this point of view, SQL and Databases per say are a data
manipulation language/design when you have data in a BLOB what are you doing
to do with it? It can't be modified or altered via SQL, so in essence its
pointless. If you have the file to insert into a BLOB then just store a
reference to that file object.
If you can give me a valid business case of storing data in this matter
which overrides the fact its bad practice then I am all ears.
N
_____
From: Adrocknaphobia [mailto:[EMAIL PROTECTED]
Sent: 21 September 2004 14:57
To: CF-Talk
Subject: Re: BLOB
>Storing data of this type in a database is not good practice, it should be
>avoided at all costs...
Your opinion doesn't necessarily = good practice.
-Adam
----- Original Message -----
From: Robertson-Ravo, Neil (RX) <[EMAIL PROTECTED]>
Date: Tue, 21 Sep 2004 14:29:23 +0100
Subject: RE: BLOB
To: CF-Talk <[EMAIL PROTECTED]>
Storing data of this type in a database is not good practice, it should be
avoided at all costs...
_____
From: Dawson, Michael [mailto:[EMAIL PROTECTED]
Sent: 21 September 2004 13:50
To: CF-Talk
Subject: RE: BLOB
Read this thread
http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=
2&threadid=795052
I'm trying to do the same thing, with little success. I can't get the
binary data inserted into SQL, however, I can use ToBase64() and insert
it, but that's not really what I want to do.
I am able to get binary data (jpgs) from a database, but I'm not able to
insert a binary file.
I hope someone can shed some light on this for us all.
Thanks
________________________________
From: Parker, Kevin [mailto:[EMAIL PROTECTED]
Sent: Monday, September 20, 2004 11:23 PM
To: CF-Talk
Subject: BLOB
How do you add a file (e.g. PDF) to SQL Server as opposed to
creating a row that you convert to a URL that links to it.
I want to create an application that includes student dossiers
so I don't want them to be locatable or downloadable by anyone or
anything other than application users. Security is at application level
and managed by the application, not directory level.
Is this the best or recommended approach.
_____________________________________
_____________________________________
_____________________________________
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
