#mysql
06 October 2007
Total 16 pages. You are browsing page 1/16.
First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last
--- Log opened Sat Oct 06 00:00:54 2007
00:03 <****> maybe in the long run, but in that case I should probably limit the amount of categories they can ascribe.
00:09 <****> simon if you use POST instead of in-URL data, faking it will be a lot harder - or at least, a lot more work
00:09 <****> so make it a form
00:11 <****> if i want a table to store a http link to picure what type of field will it be?
00:12 <****> varchar would be ok
00:12 <****> probably a varchar
00:12 <****> and the picture will show or the text?
00:12 <****> show where?
00:13 <****> that a code problem
00:13 <****> when i query the table
00:13 <****> i want the record to be a picture, title price and hyper link
00:13 <****> you will get exactly what you put in to it
00:13 <****> err
00:14 <****> if you put a string in then you get a string back
00:14 <****> if you put a jpeg in (would have to be a BLOB type) then you get a jpeg back...
00:15 <****> what do you mean blob type?
00:15 <****> however I think it is generally considered better to keep the actual jpeg on the filesystem and just store the path to it in the DB
00:15 <****> yea thats what i want
00:15 <****>
00:15 <****> if i have the query result show in html then it will show picture?
00:16 <****> Fiveohthree: http://mysqldump.azundris.com/archives/37-Serving-Images-from-a-File-System.html
00:16 <****> What if want to serve systems from an image file?
00:16 <****> what you do with it in html has nothing to do with mysql... but yes, in theory thats how it would work
00:16 <****> Fiveohthree: what is your motivation for serving out of the database?
00:16 <****> security? replication?
00:17 <****> im selling lots of items and wan
00:17 <****> want to query them with search on web site
00:17 <****> for people to shop
00:18 <****> well, obviously
00:18 <****> thats not what i was asking .. the question is why store the images in the database?
00:18 <****> generally mysql is not the place to store (large) binary data
00:18 <****> you only do this if you have a good reason
00:18 <****> like you need to replicate the binary data to many servers
00:18 <****> err he said he wanted to store them on the filesystem and store a reference in the DB
00:18 <****> and you already have mysql replication setup
00:18 <****> which is the right way(tm)
00:19 <****> or you want to get all dynamic data with one backup solution
00:19 <****> ah
00:19 <****> then all is well :)
00:19 <****> nevermind me
00:19 <****> lala
00:19 <****> at least thats how I read the conversation :)
00:19 * lsmith came late
00:19 <****> sorry i dont want to store the images in db just linkes to them
00:19 <****> just wanted to make sure that the picture would show not the link
00:19 <****> oki doki
00:21 <****> well as I said, that all depends on what you do with it in php/jsp/python/whatever. all you will get back from the database is the string you put in there. It is up to you to write the HTML around it to make it show up right
00:24 <****> does anyone know what the default charset in MySQL 4.1 is?`
00:25 <****> dfas: I don't know for sure, but from the top of my head, I think something like latin1-swedish
00:25 <****> it is
00:26 <****> CI, too - not sure about AI
00:26 <****> centosian: swedish????
00:26 <****> of course
00:26 <****> default character set is latin1, default collation is swedish_ci
00:26 <****> mysql.com is a swedish company
00:26 <****> MySQL, AB is a swedish company
00:26 <****> that, too
00:26 <****> mysql.com is a hostname
00:27 <****> don't bitch
00:27 <****> yea I know I'm swedish too.. but I thought default would be utf8 or something.
00:27 <****> dont ... say nonsense!
00:27 <****> dfas: not back in 4.1
00:27 <****> dfas: default is latin1. nothing to do with swedish
00:27 <****> dfas you can set it if you like, either on the server level, the database level, or the table level
00:27 <****> I'm half swedish... does that count?
00:27 <****> which half ?
00:28 <****> left arm, right leg, heart, liver, and one lung (I forget which one)
00:28 <****> do you guys think this is related to having wrong charset or something? "Unknown character set index for field '11316' received from server."
00:29 <****> as long as they are both latin1 then no, not related
00:29 <****> dfas: sounds to me like moving a database from a one version of mysql to an older one (or less enabled one). But that's purely a guess
00:29 <****> charset != sort order
00:29 <****> sounds like a db was copied not dumped imported
00:29 <****> collation == sort order, and sort order ONLY
00:31 <****> centosian: hm, would that be possible to solve somehow easily? changing charset or such
00:32 <****> archivist: would you elaborate that?
00:33 <****> dfas Im saying the same as centosian you data does not match your setup
00:34 <****> in which way doesnt it match?
00:35 <****> your data has a charset "Unknown character set index for field '11316'" that your server has no idea of
00:35 <****> dfas: did you copy the database from another server? And if so, did you copy the database directly, or do a dump/load?
00:36 <****> yes I did copy, from a 5.1 setup to a 4.1, and did a dump/load.
00:36 <****> ah
00:36 <****> like I said
00:36 <****> your database wants to use 5.1 features that 4.1 doesn't support
00:36 <****> oh
00:36 <****> (well that's my guess anyways)
00:37 <****> dump using --compatible=mysql40
00:37 <****> dump using --compatible=mysql41
00:37 <****> nice one archivist !
00:39 <****> hi
00:39 <****> hey
00:39 <****> that makes sense, thanks
00:39 <****> if i'm using tables with myisam, how can i make foreign keys?, if i cant, how i reference two tables?
00:39 <****> should i use innodb?
00:40 <****> yes ?
00:40 <****> joins are the same for both
00:41 <****> ?
00:41 <****> centosian: do you have any idea of what such 5.1 feature may be? any random suggestion
00:42 <****> dfas: what archivist said
00:42 <****> dfas: .frm format changed between 4.1 and 5.0
Total 16 pages. You are browsing page 1/16.
First :: Prev :: [1] [2] [3] [4] [5] [...] :: Next :: Last