| |
| |
| |
|
Page: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Comments:
<0> onlamp used to have some articles
<1> checking, thanks
<0> flupps: here's a google result, http://www.lamphowto.com/
<2> does mysql 5 have a option to use the comma join behaviour of previous version ?
<3> of course
<2> firewire: I can't find it in the docs .. .=(
<3> join syntax
<0> SELECT * FROM a, b WHERE a.id=b.fk_id
<0> is that what you're talking about?
<2> phishy: yes
<0> so i have a diagram i made with an entity that contains subentities... but whats the point of the diagram if both subentities will exist in the same table... some not using attributes in the table that are not applicable... if i'm barking up the wrong tree, point me in the right direction please ;-)
<4> generally speaking is it good to have some type of ID for each type of data?
<2> firewire: I also can't find anything about such an option there -> http://dev.mysql.com/doc/refman/5.0/en/join.html
<0> feindbild, this is right on the page
<0> SELECT t1.name, t2.salary FROM employee AS t1, info AS t2
<0> WHERE t1.name = t2.name;
<2> phishy: [20:59] <2> does mysql 5 have a option to use the comma join behaviour of previous version ?
<2> phishy: because it behaves differently in mysql 5.0 ...
<0> ok, how so?
<2> phishy: Previously, the comma operator (,) and JOIN both had the same precedence, so the join expression t1, t2 JOIN t3 was interpreted as ((t1, t2) JOIN t3). Now JOIN has higher precedence, so the expression is interpreted as (t1, (t2 JOIN t3)). This change affects statements that use an ON clause, because that clause can refer only to columns in the operands of the join, and the change in precedence changes interpretation of what those opera
<0> i see
<3> feindbild are you using using()
<2> firewire: no ...
<3> I bet you're bing bit by an optimizer change
<3> the optimizer in 5.0 has determined a better way to execute the query than 4.x did
<3> it has nothing to do with oprator precedence
<3> you can't ***ume that mysql will join your tables in the order that they appear in the query
<3> the optimizer is free to rearange them however it sees fit
<2> firewire: I'm currently wondering if I should upgrade. a lot of complex queries run way faster in 5.0, but i'd have to rewrite quite a few queries, plus the JDBC driver seems to have a few little problems with mysql 5 ....
<3> by problems with the jdbc driver you mean bugs or functionality changes?
<2> firewire: SELECT as_staff_vacation.*, as_staff.*, as_staff_vacation_types.name AS 'type_name' FROM as_staff_vacation, as_staff LEFT JOIN as_staff_vacation_types ON as_staff_vacation_types.id=as_staff_vacation.type WHERE as_staff_vacation.employee=as_staff.aid AND as_staff_vacation.id IN('81','82','83','84','85','606','349','368','388','446','509','601','622','632','696','711','803','781','816','824','855','867','878','888','1032','1400','1115'
<2> 633','1708','1709','1755','1817','1856') ORDER BY as_staff_vacation.v_from DESC, as_staff_vacation.id DESC LIMIT 0,10 <- this was a valid query up to mysql 4.1 .... but not so in 5.0 ...
<3> don't do that
<3> I'm nto even going to read it
<2> *g*
<2> sorry
<3> if the jdbc driver has bugs you should report them
<5> Yes, definitely, since bugs wrt. 5.0 and the JDBC driver would be news to me.
<5> If the above query doesn't work in 5.0, it doesn't have anything to do w/ the JDBC driver.
<3> that too
<3> feindbild is that somehow not a valid query in 5.0?
<3> and what error do you get?
<2> firewire: Unknown column 'as_staff_vacation.type' in 'on clause'
<3> do you think type might be a reserved word in 5.0?
<3> I do..
<2> hmmm ... good point ...
<0> that's better than a bug now isn't it ;-)
<2> hmm ... nope ...'SELECT type FROM `as_staff_vacation`' works fine ... so I guess its no reserved word ..
<4> should i do that once an hour?
<6>
<4> in some certain direction?
<4> cardinal ?
<2> well ... bye =)
<3> heh it isn't :)
<7> yay
<8> Can I replicate a database from 3.x to 4.x?
<9> Preference database error (insufficient permissions). Exiting abnormally
<10> Leithal just to let you know my killer bug is still alive and kicking in 1.0.5
<11> archivist: update the bug again please?
<10> Leithal 13242
<10> or do you mean update 13242 for 1.0.5
<11> right ;) note that it persists in 1.0.5
<11> I'll get them to jump on it
<11> effects lots of people now
<10> ok btw my system happily runs solidworks a 3d cad system
<9> $addrbook_global_dsn = 'mysql://username:p***word@127.0.0.1/databasename';
<9> its this right ?
<12> if using a "add page" in php, do i need to add date variable in the php that exctracts the date or does mysql do that by it self?
<13> add page?
<12> yes add entry page
<12> in php
<13> your question makes no sense
<13> maybe rephrase it?
<12> i dont know how to rephrease it
<12> do i need to add date variable in the php that exctracts the date or does mysql do that by it self?
<13> well explain what you're talking about
<12> is that better?
<13> extracts what date?
<13> from where?
<13> does mysql do what by itself?
<12> yes
<13> be specific
<12> ok from the top
<12> i am creating a blog in php
<13> if you repeat the same thing a third time I'm going to give up
<12> and using mysql to get the titles and entrys
<13> ok
<12> now, i have a table with date
<12> that keeps track of what date i have added the blog post
<14> select alias from Categories where alias <> ''; <- is there a better way to do this?
<12> now, when i do this insert, what do i need to add inorder to mysql to understand the date? i keep getting 00-00-0000
<14> date() ?
<13> johhny_b: use CURRENT_DATE
<13> and MySQL will insert the current date
<12> huh?
<12> where do add that?
<12> the row?
<13> when you're inserting
<13> insert that into the date field
<12> oh
<15> anyone here ever setup vanilla (www.getvanilla.com)???
<13> if you're using a DATETIME column, then you can use CURRENT_TIMESTAMP
<12> i am using a DATE colum
<12> but i dont understand
<12> do you mena DATE is a variable?
<13> no
<12> $CURRENT_DATE
<13> DATE is a column type
<13> CURRENT_DATE is the current date
<12> and what should i insert in to it?
<13> no
<12> ah
<12> i will try
<13> you insert CURRENT_DATE into a DATE column
<12> exacly
<12> $dateBlog = '$CURRENT_DATE';
<12> $sql = "INSERT INTO myblogs (dateBlog,title,content) VALUES ('$dateBlog','$title','$content')";
<12> -$
<16> no
<12> no?
<16> make sure to use quoting of the variables
<13> no
<13> CURRENT_DATE
<13> just like that
<16> otherwise you has nice sqlinjection available
<15> allo?
<13> !m johhny_b CURRENT_DATE
<17> johhny_b: (Date and Time Functions) : http://dev.mysql.com/doc/mysql/en/Date_and_time_functions.html
<13> INSERT INTO myblogs (dateBlog,title,content) VALUES (CURRENT_DATE,'$title','$content')
<14> what is a comment in sql?
<18> -- comment
<13> -- or (in MySQL) /* ... */
<12> Can't insert into table myblog.
<12> INSERT INTO myblogs (dateBlog,title,content) VALUES (CURRENT_DATE,'jkl','jkl')
<12> Unknown column 'dateBlog' in 'field list'
<12> Darien: your code did not work
<13> do you get an error?
<12> yes i posted it
<12> Unknown column 'dateBlog' in 'field list'
<13> so it's YOUR problem, not mine
<19> mysql> insert into t1 values (1, CURRENT_DATE, 'Phett Jao');
<19> Query OK, 1 row affected (0.00 sec)
<19> works ;)
<12> Darien: huh?
<20> is there any way to tell mysql: increment the value of X column by 3?
<12> Darien: you cant help me?
<20> johhny_b: tried `dateBlog`?
<12> redduck666: i dont understand
<13> redduck666: UPDATE table SET field = field + 3 WHERE whatever
<20> johhny_b: in your query try using `dateBlog` instead of dateBlog
Return to
#mysql
or
Go to some related
logs:
stop firefox using gmplayer
bugzilla too long for column
sloppy focus_mode auto_raise
mp3 won't play in sterio
rtusb: probe of failed with error -12
MergedFB debian etch
#debian
userfile[] javascript check
#perl
#centos
|
|