#mysql
16 October 2007
Total 19 pages. You are browsing page 5/19.
First :: Prev :: [...] [3] [4] [5] [6] [7] [...] :: Next :: Last
07:03 <****> substantially?
07:04 <****> depends
07:08 <****> max_allowed_packet -- thanks
07:13 <****> HerbM: haha bout time
07:29 <****> hi. I've managed to confuse myself a bit with DB design -- I was trying to set up a table (called audit) which is used to log messages (timestamp, description) related to rows in tables B and C. Logically, any row in tables B and C can generate more than one audit message, so B:A and C:A are non-identifying 1:n relationships
07:29 <****> but this means I have foreign keys for tables B and able C in the audit table A -- and only one of which is non-null for any given row. this seems non-normalized, somehow
07:30 <****> Do I really have to have separate audit tables for B and C?
07:41 <****> Manoj: how about creating audit table like (timestamp, sourcetable, description) for example?
07:50 <****> seekwill--
07:51 <****> moin
07:51 <****> thumbs: Guess how many points chadmaynard got in DTD??!?!??!??!?!!?
07:51 <****> chadmaynard: He's so good, he got negative points.
07:52 <****> moin moin
07:52 <****> what's the proper way to dump an entire database to a .SQL file?
07:53 <****> I am the supreme player
07:53 <****> how very strange. my capslock just came on, and i'm reasonably certain i hadn't pressed the capslock key.
07:53 <****> Phuzion: mysqldump
07:53 <****> so, the syntax would be mysqldump -u username -ppassword database, correct?
07:53 <****> seekwill: I just have better things to do than play. You know a girlfriend.
07:54 <****> chadmaynard: Uh huh, right ;)
07:54 <****> file.sql
07:54 <****> seekwill: you're just mad because ruby won't talk to you anymore.
07:54 <****> she loves me now
07:54 <****> haha
07:54 <****> :(
07:55 * seekwill goes off and cries
07:55 * chadmaynard sticks tongue out
07:55 <****> don't worry i will send some asians your way
07:55 <****> Toss my salad !
07:55 <****> Only the crazy nes
07:55 <****> don't worry i will send some crazy asians your way
07:55 <****> i know a lot of crazy asians. Should be easy
07:57 <****> he just stole all of the sense of triumph out of that realisation.
07:58 <****> what are you talking about
08:48 <****> let's say I was selling candles and I had over 50 different types of scents and I was creating a products table, would I enter each scent individually in a set?
08:49 <****> morning
08:49 <****> would I create another table called "scents" and give each scent a unique #?
08:49 <****> and use that unique # in my products.scents?
08:49 <****> set is for multiple values, enum is for 1 value
08:50 <****> well I would have to do 'apple','apple cider','banana','blueberry'
08:50 <****> it would 50 of them
08:50 <****> 50 of them, but will a candle contain 1 or more than 1?
08:50 <****> i need a little help with the WHERE part of my syntax, how would i use WHERE to sellect only the records of tbl_shipping_numbers where the code_ID = tbl_shipping_codes.ID (think ive answere my own question there but not fully)
08:50 <****> just 1
08:50 <****> then use enum instead of set
08:50 <****> SELECT tbl_shipping_numbers.ID, tbl_shipping_numbers.Code_Id, tbl_shipping_numbers.number, tbl_shipping_code.Id FROM tbl_shipping_numbers LEFT JOIN tbl_shipping_code ON tbl_shipping_numbers.Code_Id = tbl_shipping_code.Id
08:51 <****> if you need to store other information of the scent, then use a separate table
08:51 <****> but should I just create a table called scents instead? and give each scent a unique # ?
08:51 <****> select * FROM products WHERE scent = 3
08:52 <****> if you have other properties of the scent that you want to store
08:52 <****> otherwise enum data type works well
08:52 <****> no, I just have the scent name but creating an ENUM with 50 options seems a bit overkill no?
08:52 <****> not overkill
08:52 <****> enum can have up to 65535 values
08:52 <****> for data entry purposes
08:53 <****> and displaying purposes
08:53 <****> but if you need to keep adding new scent, then a table is better
08:54 <****> it is *okay* to have a table that is simply id,name
08:55 <****> nothing wrong with that
08:56 <****> last question, is there a name for that type of table?
08:56 <****> a small one ^_^
08:56 <****> :o
08:59 <****> Hi! I' d like mysql to listen on 127.0.0.1, and on an external IP. How can i give two parameters to bind-address? So what delimeter should i use?
09:01 <****> Actually this is a Linux system.
09:02 <****> ertg: why not just the external ip ?
09:02 <****> you can connect to that locally also
09:03 <****> default is all ip
09:04 <****> either bind to 1 or all
09:05 <****> Dynom: well, i can connect then somehow with mysql, but if i try telnet localhost 3306, it will give back connection refused. Why?
09:06 <****> there is an alternative to port 3306 :)
09:09 <****> moin
09:12 <****> ertg: because localhost == 127.0.0[.1]
09:12 <****> so connect to the hostname of the server
09:13 <****> localhost is not equal to 127.0.0.1 to mysql
09:13 <****> e.g. hostname is: mysql01.mycompany.com
09:13 <****> try the hostname in mysql -h and it probably fail
09:13 <****> so localhost should find the mysqld bound to the external ip ?
09:14 <****> localhost does not care about the ip binding or the ip at all
09:15 <****> Hi all
09:15 <****> there is a table with numeric id's in the first column (unique) and second column with some data in it
09:16 <****> now I want to obtain the record with the highest numeric value in first column
09:16 <****> just the highest value is also fine (better actually)
09:16 <****> what would be the command ?
09:16 <****> select statement of course
09:17 <****> I am just starting with sql, so if you could be more explicit ?
09:17 <****> learn the select statement then
09:18 <****> !m sobers_2002 tutorial
09:18 <****> sobers_2002: (MySQL Tutorial) : http://dev.mysql.com/doc/mysql/en/tutorial.html
09:19 <****> in the case of candles... what if you sell candles & candle holders.. . should you place everything in 1 product table?
09:20 <****> candles have specific traits like uhh wax type, scent, type of candle
09:20 <****> candle holders don't.
09:20 <****> consider the sales table, how do you record sales?
09:20 <****> I guess it would be product #
09:20 <****> consider product table, how do you store product info
09:21 <****> are product tables known to be long and full of default values set to No?
09:21 <****> what if you start to add a 3rd product
09:21 <****> will it fit into your product table
09:21 <****> of course not
09:21 <****> ill have to add on to the product table new *traits*
09:22 <****> making my product table a huge mess eventually
Total 19 pages. You are browsing page 5/19.
First :: Prev :: [...] [3] [4] [5] [6] [7] [...] :: Next :: Last