How is it not suited?
I stopped using mySQL to store images because of
browser refresh problems, but other than that --
I didn't find any major problems with using it.
Plus, moving images from one system to another
was much easier because you just moved the dB and
you don't have to worry about
How is it not suited?
I stopped using mySQL to store images because of
browser refresh problems, but other than that --
I didn't find any major problems with using it.
Plus, moving images from one system to another
was much easier because you just moved the dB and
you don't have to worry about
At 11:07 PM +0200 5/11/06, Jochem Maas wrote:
I think you make interesting points Tedd, it's given me stuff to
think about anyway.
leveraging a Db for image storage can have advantages but
implementing it correctly
takes a stack more knowledge and more work to do it correctly,
therefore the re
tedd wrote:
At 1:02 AM +1000 5/11/06, Peter Hoskin wrote:
Despite common belief, SQL is not suited to the storage of binary files.
SQL is based on ASCII.
Store your files on the filesystem, not SQL.
How is it not suited?
I stopped using mySQL to store images because of browser refresh
prob
At 1:02 AM +1000 5/11/06, Peter Hoskin wrote:
Despite common belief, SQL is not suited to the storage of binary files.
SQL is based on ASCII.
Store your files on the filesystem, not SQL.
How is it not suited?
I stopped using mySQL to store images because of
browser refresh problems, but other
Jochem Maas wrote:
thank you Edward.
...
there is a funny little story about where the name BLOB came from:
http://www.cvalde.net/misc/blob_true_history.htm
just to note that BLOBs where invented by the guy that designed Interbase
which just happens to be the ancestor of the coolest DBMS
thank you Edward.
Edward Vermillion wrote:
>
> On May 10, 2006, at 10:53 AM, Peter Hoskin wrote:
>
>>
>> GOOGLE DO NOT ARGUE
>
>
> o_O?
yeah! I did figure it really was about time they changed their
'Do No Evil' slogan given their escapades in china
funnily enough I watched a documentary th
There are names for people who use the blob field of a MySQL db to store
images.
Moron, and Idiot are just two examples, but if other circumstances exist,
you can say newbie as well. As a newbie I thought myself that storing images
in a DB would be a nice clean solution. Voices of experience said
On Wed, May 10, 2006 9:52 am, Renzo Clavijo wrote:
> I'm gonna be more precise:
>
> I wrote a form with fields , then i need to
Should be know how
> to upload the files to the MySQL server (postgreSQL wold be
> appreciated). It
> implies: Which field(s) must have the table where I'll save the
> i
On May 10, 2006, at 10:53 AM, Peter Hoskin wrote:
GOOGLE DO NOT ARGUE
o_O?
So, if ASCII and Binary are both codesets... which does SQL use to
store
its data?
ASCII is a codeset, utf* is a codeset binary is a, um... , binary
data.
varchar, etc => ASCII/utf*/whatever => st
Jochem Maas wrote:
> Peter Hoskin wrote:
>> Renzo Clavijo wrote:
>>
>>> hi all..
>>>
>>> I'm gonna be more precise:
>>>
>>> I wrote a form with fields , then i need to
>>> know how
>>> to upload the files to the MySQL server (postgreSQL wold be
>>> appreciated). It
>>> implies: Which field(s) mus
Peter Hoskin wrote:
Renzo Clavijo wrote:
hi all..
I'm gonna be more precise:
I wrote a form with fields , then i need to
know how
to upload the files to the MySQL server (postgreSQL wold be
appreciated). It
implies: Which field(s) must have the table where I'll save the
image?. Is
there an ex
Peter Hoskin schrieb:
But mysql can be quite a good spool though.
That way you don't have to code one for yourself.
That does not mean that there are not SIGNIFICANT ADVANTAGES to coding
something to use the filesystem - such as seek speed. When dealing with
large datasets of binary, filesyste
> But mysql can be quite a good spool though.
>
> That way you don't have to code one for yourself.
>
That does not mean that there are not SIGNIFICANT ADVANTAGES to coding
something to use the filesystem - such as seek speed. When dealing with
large datasets of binary, filesystems are much quicke
Peter Hoskin schrieb:
Renzo Clavijo wrote:
hi all..
I'm gonna be more precise:
I wrote a form with fields , then i need to
know how
to upload the files to the MySQL server (postgreSQL wold be
appreciated). It
implies: Which field(s) must have the table where I'll save the
image?. Is
there an e
Renzo Clavijo wrote:
> hi all..
>
> I'm gonna be more precise:
>
> I wrote a form with fields , then i need to
> know how
> to upload the files to the MySQL server (postgreSQL wold be
> appreciated). It
> implies: Which field(s) must have the table where I'll save the
> image?. Is
> there an exampl
Angelo Zanetti
Z Logic
www.zlogic.co.za
[c] +27 72 441 3355
[t] +27 21 469 1052
Jasper Bryant-Greene wrote:
> [EMAIL PROTECTED] wrote:
>
>> Well basically i need it for an "add products" page and if the users
>> doesnt fill
>> in all the fields correctly I display some error message as well as
[EMAIL PROTECTED] wrote:
Well basically i need it for an "add products" page and if the users doesnt fill
in all the fields correctly I display some error message as well as populate the
textfields and dropdown lists with the values they previously entered, so if
they entered/selected the file I
IMHO this is just a design issue, why not just hide the upload field,
display a message that they need not re-upload, and just add a hidden
field with the name of the uploaded file and once they've corrected
their fields, they re-post, and viola, you've got your file still.
[EMAIL PROTECTED] wrote
<[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Thanks for the replies.
>
> Well basically i need it for an "add products" page and if the users
doesnt fill
> in all the fields correctly I display some error message as well as
populate the
> textfields and dropdown lists with the valu
Thanks for the replies.
Well basically i need it for an "add products" page and if the users doesnt fill
in all the fields correctly I display some error message as well as populate the
textfields and dropdown lists with the values they previously entered, so if
they entered/selected the file I wa
>> The uploaded file name will be $HTTP_POST_FILES["filename"]["name"] -- use
>> that rather than $_POST["filename"].
>
> I'm sorry I don't understand. What is the extra ["name"] for? When I use
> this in the insert into the value that is inserted into the database is
> Array, as opposed to the ac
On Sunday 21 March 2004 22:53, Vernon wrote:
> > The uploaded file name will be $HTTP_POST_FILES["filename"]["name"] --
> > use that rather than $_POST["filename"].
>
> I'm sorry I don't understand. What is the extra ["name"] for? When I use
> this in the insert into the value that is inserted into
> The uploaded file name will be $HTTP_POST_FILES["filename"]["name"] -- use
> that rather than $_POST["filename"].
I'm sorry I don't understand. What is the extra ["name"] for? When I use
this in the insert into the value that is inserted into the database is
Array, as opposed to the actual filen
> All I am trying to do is insert the file name, not the file. The file is
> being uploaded to the server in a specific location. All I need is the
> filename inserted into the database. I've gotten the upload part to work and
> everything I just can't get the file name inserted for God knows what
25 matches
Mail list logo
