Re: how things get messed up

2010-02-23 Thread Vikram A
: how things get messed up I thought I had replied publicly to Johan’s suggestion, with some personal experience. He’s absolutely right, that would give you a solution that would be completely transparent to your application and therefore much easier to implement. You could keep re-arranging your

RE: how things get messed up

2010-02-22 Thread Jerry Schwartz
, 2010 11:17 PM To: Jerry Schwartz Cc: Johan De Meersman Subject: Re: how things get messed up Dear Sir, I agree with the solution proposed. But one of the member[Johan De Meersman ] of this list has commented it. Do you have any opposition/Suggestions? Thank you VIKRAM A _ From

Re: how things get messed up

2010-02-18 Thread Johan De Meersman
*cough*partitioning*cough* On Thu, Feb 18, 2010 at 5:24 PM, Jerry Schwartz wrote: > From: Vikram A [mailto:vikkiatb...@yahoo.in] > Sent: Wednesday, February 17, 2010 11:41 PM > To: Jerry Schwartz > Cc: MY SQL Mailing list > Subject: Re: how things get messed up > > > >

RE: how things get messed up

2010-02-18 Thread Jerry Schwartz
From: Vikram A [mailto:vikkiatb...@yahoo.in] Sent: Wednesday, February 17, 2010 11:41 PM To: Jerry Schwartz Cc: MY SQL Mailing list Subject: Re: how things get messed up Dear Jerry Schwartz We have applications for colleges in India. The same idea of having single table for manipulating

Re: how things get messed up

2010-02-18 Thread Martijn Tonies
We have applications for colleges in India. The same idea of having single table for manipulating students records. but we are not following archiving >concept. Ex stupersonal. and stuclass these tables are playing wide role in our application. After 7 years now there are 9000 records[postgres

Re: how things get messed up

2010-02-17 Thread Vikram A
:22 PM Subject: RE: how things get messed up >-Original Message- >From: Vikram A [mailto:vikkiatb...@yahoo.in] >Sent: Friday, February 12, 2010 4:13 AM >To: Johan De Meersman >Cc: MY SQL Mailing list >Subject: Re: how things get messed up > >Sir, > >Thanks for y

Re: how things get messed up

2010-02-17 Thread Barry Leslie
n'aura pas n'importe > quel effet légalement obligatoire. Étant donné que les email peuvent > facilement être sujets à la manipulation, nous ne pouvons accepter aucune > responsabilité pour le contenu fourni. > > > > > >> From: jschwa...@the-infoshop.com

Re: how things get messed up

2010-02-16 Thread Paul McCullagh
Just like to mention that http://www.blobstreaming.org was created to solve this problem in MySQL. The Launchpad project is here: https://launchpad.net/pbxt On Feb 16, 2010, at 3:23 PM, Johan De Meersman wrote: On Mon, Feb 15, 2010 at 10:53 AM, Martijn Tonies wrote: databases are made

RE: how things get messed up

2010-02-16 Thread Martin Gainty
u fourni. > From: jschwa...@the-infoshop.com > To: vikkiatb...@yahoo.in; vegiv...@tuxera.be > CC: mysql@lists.mysql.com > Subject: RE: how things get messed up > Date: Tue, 16 Feb 2010 11:02:22 -0500 > > >-Original Message- > >From: Vikram A [mailto:vikk

RE: how things get messed up

2010-02-16 Thread Jerry Schwartz
>-Original Message- >From: Vikram A [mailto:vikkiatb...@yahoo.in] >Sent: Friday, February 12, 2010 4:13 AM >To: Johan De Meersman >Cc: MY SQL Mailing list >Subject: Re: how things get messed up > >Sir, > >Thanks for your suggestion, >I will go for blob stor

RE: how things get messed up

2010-02-16 Thread Jerry Schwartz
>-Original Message- >From: Ann W. Harrison [mailto:a...@mysql.com] >Sent: Monday, February 15, 2010 12:12 PM >To: Martijn Tonies >Cc: mysql@lists.mysql.com >Subject: Re: how things get messed up > >There are lots of ways to screw up storage. > [JS] As the on

Re: how things get messed up

2010-02-16 Thread Johan De Meersman
On Mon, Feb 15, 2010 at 6:11 PM, Ann W. Harrison wrote: > And here's a comment from a very experienced MySQL DBA > > http://sheeri.com/archives/39 Not so much a comment as her starting up the same discussion we're having :-) If you have the kind of needs where replicating NFS servers won't ho

Re: how things get messed up

2010-02-16 Thread Johan De Meersman
On Mon, Feb 15, 2010 at 10:53 AM, Martijn Tonies wrote: > databases are made for storing data - it saves you on both database and PHP >> requests, as (from a web point of view) you can't return the image data >> inside your HTML - it requires a second HTTP call. Filesystem image >> serving, >> > >

Re: how things get messed up

2010-02-15 Thread Ann W. Harrison
Martijn Tonies wrote: For example, the Firebird DBMS stores (longer) Blob data not right there in the record, so whenever you don't request the blob (that is, not selecting it), it ignores it completely and it can go through the file quickly. As do most of the MySQL storage engines. InnoD

Re: how things get messed up

2010-02-15 Thread Martijn Tonies
Hi Ann, From: "Ann W. Harrison" Martijn Tonies wrote: For example, the Firebird DBMS stores (longer) Blob data not right there in the record, so whenever you don't request the blob (that is, not selecting it), it ignores it completely and it can go through the file quickly. As do most of t

Re: how things get messed up

2010-02-15 Thread Martijn Tonies
I am in the situation to storing student and staff images. every year 2000 new photos has to be added in our application. Can i have your suggestion, which is the best one, storing as a blob Or using NFS? It will be great help to me, because such experts are sharing your own experience on this

Re: how things get messed up

2010-02-15 Thread Martijn Tonies
Sounds logical, what's also nice to see, is that even though people here tend to say "don't put binaries in the database", apparently Facebook thought it would be nice to do so (for all sorts of reasons) and even took the time to write their own blob storage mechanism ;-) The whole point is t

Re: how things get messed up

2010-02-12 Thread Ann W. Harrison
Martijn Tonies wrote: For example, the Firebird DBMS stores (longer) Blob data not right there in the record, so whenever you don't request the blob (that is, not selecting it), it ignores it completely and it can go through the file quickly. As do most of the MySQL storage engines. Cheers,

Re: how things get messed up

2010-02-12 Thread Vikram A
From: Johan De Meersman To: Vikram A Cc: MY SQL Mailing list Sent: Fri, 12 February, 2010 2:23:01 PM Subject: Re: how things get messed up On Fri, Feb 12, 2010 at 9:19 AM, Vikram A wrote: I am in the situation to storing student and staff images. every year 2000 new photos has to be added

Re: how things get messed up

2010-02-12 Thread Johan De Meersman
On Fri, Feb 12, 2010 at 9:19 AM, Vikram A wrote: > I am in the situation to storing student and staff images. every year 2000 > new photos has to be added in our application. > > Can i have your suggestion, which is the best one, storing as a blob Or > using NFS? > It will be great help to me, be

Re: how things get messed up

2010-02-12 Thread Vikram A
on this binary storage issue. Thank you. VIKRAM A From: Johan De Meersman To: Martijn Tonies Cc: mysql@lists.mysql.com Sent: Fri, 12 February, 2010 1:09:32 PM Subject: Re: how things get messed up On Fri, Feb 12, 2010 at 8:27 AM, Martijn Tonies wrote

Re: how things get messed up

2010-02-11 Thread Johan De Meersman
On Fri, Feb 12, 2010 at 8:27 AM, Martijn Tonies wrote: > Sounds logical, what's also nice to see, is that even though people here > tend to say "don't put binaries in the database", apparently Facebook > thought it would be nice to do so (for all sorts of reasons) and even took > the time to write

Re: how things get messed up

2010-02-11 Thread Martijn Tonies
On Fri, Feb 12, 2010 at 8:05 AM, Martijn Tonies wrote: Firebird uses 1 or multiple files per database, not per table, this file has a special "blob area", so to speak, and the records include a "blob ID". When a client/stored routine selects a blob that isn't available in the record data (sto

Re: how things get messed up

2010-02-11 Thread Johan De Meersman
On Fri, Feb 12, 2010 at 8:05 AM, Martijn Tonies wrote: > Firebird uses 1 or multiple files per database, not per table, this file > has > a special "blob area", so to speak, and the records include a "blob ID". > > When a client/stored routine selects a blob that isn't available in the > record >

Re: how things get messed up

2010-02-11 Thread Martijn Tonies
[JS] Storing BLOBs in a table must slow down the inner workings of the database engine. After all, the tables are really disk files under the covers. Can the database engine read only parts of a file record? Jerry Schwartz Well, there's where things go wrong -- first of all, a "database engi

Re: how things get messed up

2010-02-11 Thread Johan De Meersman
On Thu, Feb 11, 2010 at 5:24 PM, Jerry Schwartz wrote: > [JS] Storing BLOBs in a table must slow down the inner workings of the > database engine. After all, the tables are really disk files under the > covers. > Can the database engine read only parts of a file record? > They recently invented t

RE: how things get messed up

2010-02-11 Thread Jerry Schwartz
>> [JS] Storing BLOBs in a table must slow down the inner workings of the >> database engine. After all, the tables are really disk files under the >> covers. >> Can the database engine read only parts of a file record? >> >> Jerry Schwartz > >Well, there's where things go wrong -- first of all, a

Re: how things get messed up

2010-02-11 Thread Martijn Tonies
I think store files in DB has no complicated reasons, just for convenience. For example, I might make files automatically be backup-ed, and no budget for an independent backup solution. Thanks. Cui [JS] Storing BLOBs in a table must slow down the inner workings of the database engine. After

Re: how things get messed up

2010-02-11 Thread Jochem van Dieten
On 2/10/10, Ilya Kazakevich wrote: > There was a joke in russian PHP club: "why strore images in database? Are > you going to have a full text search on them?" Yes. That is what EXIF data is for, isn't it? And considering this is about PDFs any inability of a database engine to do a full text sea

Re: how things get messed up

2010-02-11 Thread Joerg Bruehe
Hi Ilya, everybody! Ilya Kazakevich wrote: > [[...]] > > IMHO: > Storing files in DB is probably bad idea. > Here are some advantages of storing files on filesystem: > [[...]] We could discuss them individually, but I agree several of your points are valid. The remaining question is which impor

RE: how things get messed up

2010-02-11 Thread Jerry Schwartz
>-Original Message- >From: John G. Heim [mailto:jh...@math.wisc.edu] >Sent: Wednesday, February 10, 2010 2:09 PM >To: mysql@lists.mysql.com >Subject: how things get messed up >It is amazing how often quick & dirty turns out just being >dirty in the end. > >

RE: how things get messed up

2010-02-11 Thread Jerry Schwartz
>-Original Message- >From: Cui Shijun [mailto:rancp...@gmail.com] >Sent: Wednesday, February 10, 2010 10:53 PM >To: Ilya Kazakevich >Cc: John G. Heim; mysql@lists.mysql.com >Subject: Re: how things get messed up > >Hello Ilya, > I think store files in DB has n

Re: how things get messed up

2010-02-11 Thread David Giragosian
On Thu, Feb 11, 2010 at 8:56 AM, Martijn Tonies wrote: > Hello John, > > About 5 years ago, I was asked to write a php app for my department. The >> app keeps track of graduate school applicants to my department at the >> university. The main data elements are the scores each professor gives to >

Re: how things get messed up

2010-02-11 Thread Martijn Tonies
Hello John, About 5 years ago, I was asked to write a php app for my department. The app keeps track of graduate school applicants to my department at the university. The main data elements are the scores each professor gives to each applicant. There are only about 400 applicants each year so

Re: how things get messed up

2010-02-10 Thread Cui Shijun
be deleted automatically using foreign keys, but you have to > do it in your app if files are stored externally. > > If somebody knows more reasons to store files in DB -- post it here, please. > It would be interesting. Thanks. > > Ilya. > > -Original Message----- > F

RE: how things get messed up

2010-02-10 Thread Ilya Kazakevich
if files are stored externally. If somebody knows more reasons to store files in DB -- post it here, please. It would be interesting. Thanks. Ilya. -Original Message- From: John G. Heim [mailto:jh...@math.wisc.edu] Sent: Wednesday, February 10, 2010 10:09 PM To: mysql@lists.mysql.co

Re: how things get messed up

2010-02-10 Thread Buford Tannen
John G. Heim wrote: About 5 years ago,... then the selection committee asked me to add something ... Then the next year, the graduate school changed their ... Then they started taking letters of recommendation ... One might think of this as scope-creep, but really, given the length of time ove

how things get messed up

2010-02-10 Thread John G. Heim
About 5 years ago, I was asked to write a php app for my department. The app keeps track of graduate school applicants to my department at the university. The main data elements are the scores each professor gives to each applicant. There are only about 400 applicants each year so even with all