This may be too obvious, but what is in that text field?
Regards,
Jerry Schwartz
Global Information Incorporated
195 Farmington Ave.
Farmington, CT 06032
860.674.8796 / FAX: 860.674.8341
> -----Original Message-----
> From: Ted Johnson [mailto:whatawonderfulworldweliveintoo@stripped]
> Sent: Monday, October 16, 2006 3:57 AM
> To: Dan Buettner
> Cc: mysql@stripped
> Subject: Re: Re: Re: Re: Readind a Dump W/o Expanding It
>
> 8080The data field's a text field, not a blob! That's the
> problem, there are no blobs, and I just wanted a second set
> of eyes on this to confirm what simply makes no sense at all!
> I'd love to know where the dickens those images went!!
>
> Thanks anyway,
> Ted
>
> ----- Original Message ----
> From: Dan Buettner <drbuettner@stripped>
> To: Ted Johnson <whatawonderfulworldweliveintoo@stripped>
> Cc: mysql@stripped
> Sent: Sunday, October 15, 2006 8:45:07 PM
> Subject: Re: Re: Re: Re: Readind a Dump W/o Expanding It
>
> Ted - sorry, not sure what this is showing me. Is the image data
> supposed to be in the "data" field in the Photo table? It's not
> there, or it's corrupt?
>
> Dan
>
>
> On 10/15/06, Ted Johnson
> <whatawonderfulworldweliveintoo@stripped> wrote:
> >
> > 74
> > ----- Original Message ----
> > From: Dan Buettner <drbuettner@stripped>
> > To: Ted Johnson <whatawonderfulworldweliveintoo@stripped>
> > Cc: mysql@stripped
> > Sent: Sunday, October 15, 2006 9:22:04 AM
> > Subject: Re: Re: Re: Readind a Dump W/o Expanding It
> >
> > How were they stored in the database?
> >
> > You got me on that. I just took over this box. Here's what
> my queries show:
> >
> > server167# mysqlshow -uroot -p tirekingdom
> > Enter password:
> > Database: tirekingdom
> > +--------------------+
> > | Tables |
> > +--------------------+
> > | OrderItem |
> > | Orders |
> > | Photo |
> > | PhotosForTire |
> > | PhotosForWheel |
> > | Shopper |
> > | Tire |
> > | Vehicle |
> > | Wheel |
> > | WheelMake |
> > | WheelsForWheelMake |
> > +--------------------+
> > server167# mysqlshow tirekingdom Photo -uroot -p
> > Enter password:
> > Database: tirekingdom Table: Photo Rows: 2160
> >
> +-------+-------------+-------------------+------+-----+------
> ---+-------+---------------------------------+---------+
> > | Field | Type | Collation | Null | Key |
> Default | Extra |
> > Privileges | Comment |
> >
> +-------+-------------+-------------------+------+-----+------
> ---+-------+---------------------------------+---------+
> > | oid | int(11) | NULL | | PRI | 0
> | |
> > select,insert,update,references | |
> > | Data | mediumtext | latin1_swedish_ci | YES | |
> | |
> > select,insert,update,references | |
> > | Type | varchar(4) | latin1_swedish_ci | YES | |
> | |
> > select,insert,update,references | |
> > | Name | varchar(32) | latin1_swedish_ci | YES | |
> | |
> > select,insert,update,references | |
> >
> +-------+-------------+-------------------+------+-----+------
> ---+-------+---------------------------------+---------+
> > server167# mysqlshow tirekingdom PhotoForTires -uroot -p
> > Enter password:
> > mysqlshow: Cannot list columns in db: tirekingdom, table:
> PhotoForTires:
> > Table 'tirekingdom.PhotoForTires' doesn't exist
> > server167# mysqlshow -uroot -p tirekingdom PhotosForTire
> > Enter password:
> > Database: tirekingdom Table: PhotosForTire Rows: 1058
> >
> +---------+---------+-----------+------+-----+---------+------
> -+---------------------------------+---------+
> > | Field | Type | Collation | Null | Key | Default | Extra |
> > Privileges | Comment |
> >
> +---------+---------+-----------+------+-----+---------+------
> -+---------------------------------+---------+
> > | TireID | int(11) | NULL | | PRI | 0 | |
> > select,insert,update,references | |
> > | PhotoID | int(11) | NULL | | PRI | 0 | |
> > select,insert,update,references | |
> >
> +---------+---------+-----------+------+-----+---------+------
> -+---------------------------------+---------+
> > server167# mysqlshow -uroot -p tirekingdom PhotosForWheel
> > Enter password:
> > Database: tirekingdom Table: PhotosForWheel Rows: 1098
> >
> +---------+---------+-----------+------+-----+---------+------
> -+---------------------------------+---------+
> > | Field | Type | Collation | Null | Key | Default | Extra |
> > Privileges | Comment |
> >
> +---------+---------+-----------+------+-----+---------+------
> -+---------------------------------+---------+
> > | WheelID | int(11) | NULL | | PRI | 0 | |
> > select,insert,update,references | |
> > | PhotoID | int(11) | NULL | | PRI | 0 | |
> > select,insert,update,references | |
> >
> +---------+---------+-----------+------+-----+---------+------
> -+---------------------------------+---------+
> >
> > So, where's the blob? It isn't in some file in the site,
> I've checked.
> >
> > Which way did you end up restoring the data?
> >
> > The first way you recommended. Using vi, I opened the file,
> set "ma" at the
> > top, searched for the top of the database, entered "d`a" to delete
> > everything above, searched for the bottom of the database,
> set "ma", entered
> > G to go to the bottom, then "d`a" to delete everything
> else. It was a little
> > more complicated than that, but with those steps involved.
> >
> > And the dumpfile you have - how has it been handled? I ask
> because if it
> > contains binary data and was FTP'd from one machine to
> another the wrong
> > way, that could have done it.
> >
> > No, it was there in the box all along.
> > TIA,
> > Ted
> >
> >
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql110
> To unsubscribe:
> http://lists.mysql.com/mysql?unsub=1
> too@stripped
>
>
>
>
>
>
>
>