Yakulis: Isn’t that the case of.banks ? 😮
Manross: Yakulis: because people type too slowly
Yakulis: Manross: ah, i don’t think that will bother the user no ?
Varieur: Yakulis: how many rows do banks have?
Yakulis: Varieur: i would say millions :p
Varieur: Yakulis: maybe. Maybe more.
Manross: Yakulis: that’s 1/4 of a second. people don’t notice
Yakulis: Manross: ah, that’s reasonable
Manross: Yakulis: this.timeoutId = window.setTimeoutfunction {$.get”ajax_search.php”, { t: x }, functiondata{ $’#searchquote’.htmldata };}, 250;
Yakulis: Manross: yeah thanls .
Manross: Yakulis: actually it protects your mysql server from the fast typers. and you can play with the delay
Yakulis: Manross: ah yes, good idea the code :p
Varieur: Yeah, it protects your server from fast typers like me
Yakulis: Manross: shouldn’t one worry about js’s presence?
Manross: I’m not sure what you mean
Yakulis: I mean js-support in the browser
Yakulis: Dunno.aren’t there users who disable js support in their browsers? :p
Manross: Yakulis: I would bet you that js on the client and the server is the future
Manross: Yakulis: I am adjusting my work for that
Varieur: It’s a one-time verification key.
Yakulis: Ah it’s the registration :v
Ramage: In mysql 5.6, can you resignal exception in exit handler after catching one raised by 45000 and transactional rollback?
Manross: Speak of the devil. look what just showed up – http://developers.slashdot.org/story/15/09/05/1843238/php-70-nearing-release-performance-almost-as-good-as-hhvm
Varieur: Manross: don’t tell domas
Manross: Varieur: all scripting languages are hailed as saviors, then cursed as failures, then replaced. lather, rinse, repeat.
Manross: Varieur: the only people who benefit are the ones running code bootcamps :-
Culbreath: What is “produced” by GROUP BY?
Culbreath: What sort of intermediate form comes about
Culbreath: For example what if I did SELECT name FROM People GROUP BY department
Kanahele: Culbreath: Most implementations of sql don’t allow the mixing of grouped and ungrouped columns in the SELECT clause. mysql does, but the row selected for the ungrouped column is an unpredictable value. The groupwise max solution is a way to specify the value selected for the ungrouped column.
Maccormack: Culbreath: It’s “groupwise max” ! — just this once . http://jan.kneschke.de/projects/mysql/groupwise-max/ http://dev.mysql.com/doc/refman/5.6/en/example-maximum-column-group-row.html
Schweyen: Culbreath: http://jan.kneschke.de/projects/mysql/groupwise-max/ http://dev.mysql.com/doc/refman/5.6/en/example-maximum-column-group-row.html
Manross: Culbreath: that is an abuse of the GROUP BY clause
Culbreath: Ok, let me look into those
Manross: Culbreath: select name, count* from t1 group by name; — a valid use of GROUP BY and an aggregate function
Manross: Culbreath: there is a sql_mode server setting to insist that mysql conform to the sql standard. https://dev.mysql.com/doc/refman/5.6/en/sql-mode.html#sqlmode_only_full_group_by
Culbreath: Manross: that makes sense. I suppose a query like the one I write shouldn’t make sense
Manross: Culbreath: you cannot rely on the result
Manross: Culbreath: and yet it provides a result.
Manross: Culbreath: bad mojo :-/
Culbreath: If I do Having name = ‘sandy’, does that mean any of the tuples returned by GROUP BY will not be elliminated if they were formed using a tuple where name=’sandy’?
Varieur: Culbreath: don’t use HAVING yet until you understand aggregation
Hals: Having is like ‘where’ for ‘group by’
Culbreath: Varieur: Not sure I have a choice, trying to understand the material given by our instructor =