Tum: yes, you can achieve.

Varieur: Ruibritopt: those limits are do***ented too.

Rosenheim: Varieur: from https://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits i can see that most file systems have an unlimited maximum pathname lenght

Varieur: Ruibritopt: what filesystem is your server os using?

Basua: Varieur: I am using NodeJS which can them be deployed on any Server. I dont know before hand

Laven: Varieur: but these files dont have to be necessary on the NODEJS root folder, they can be anywhere in the system

Varieur: Look at practical limits, then

Varieur: Does a 1024 characters path make sense?

Hoeller: It is the value i decided before asking the question in the channel

Carvett: In fact i believe even 254 would be more than enough

Dragich: 1024 just to be on the safe side i guess, but 254 should suffice for most cases, do you agree thumbs

Varieur: If you want to really sleep at night, just use 2048!

Hommell: Hahahah i will take you advice, but do you have any reasoning behind that? just in case I need to argue that number

Varieur: I looked for the longest path on my servers.

Jernstrom: Varieur: thanks for the help and for doing that. i will take the 2048 :

Silvester: Seems to be more than enough

Varieur: Ruibritopt: I’m at 315 or so.

Wallaert: I have a query that is quite slow 15-20s and I’d like to improve its performance

Nevill: Query, indexes, and table sizes can be found at https://gist.github.com/tummykung/81b86e41e6fb2b3edc21

Varieur: Tum: well, first, stop using show indexes

Varieur: Tum: use SHOW CREATE TABLE tblG, and use EXPLAIN

Varieur: Tum: add the sql, the show create table, and explain output to the same gist

Soyke: Oh, what’s bad about show index?

Grigaliunas: But yeah I’ll add the commands you suggested

Varieur: Tum: it doesn’t show the data type for the columns. SHOW CREATE TABLE does both.

Trexel: Varieur: new outputs added. Link to gist: https://gist.github.com/tummykung/81b86e41e6fb2b3edc21

Varieur: Tum: let’s get rid of the useless stuff, like SHOW INDEX. Also, you didn’t show the EXPLAIN output.

Wallner: Varieur: ok, updated. Hit refresh

Varieur: Tum: run EXPLAIN on the sql, silly.

Winslow: Tum: See http://dev.mysql.com/doc/refman/5.6/en/using-explain.html

Varieur: Tum: start with key: NULL

Varieur: Tum: also, your Course derived table is pretty large 1434601 rows

Varieur: Tum: and “usingCRSE_ID, STRM, CL***_SECTION, {SETUP} Setup” isn’t valid sql.

Citron: Where did I derive my Course table?

Varieur: Tum: no idea. You didn’t show the real sql yet,

Varieur: Tum: and remove the EXPLAIN tbl; from that gist – it’s pointless

Britson: Re: {SETUP} Setup” isn’t valid sql. Why not. It runs.

Varieur: Tum: FROM a JOIN b USING , nonsense AS c needs to be rewritten

Syas: The nonsense is necessary, as it computes the value that needs to be used

Varieur: Tum: are you trying to write a cross join? It’s not clear from the broken sql you showed

Scarpati: Varieur: I have a real sql in the gist

Miran: What is a cross join?

Copelin: The nonsense is to setup variables to use later

Varieur: Tum: you want the total to show on each row?

Kohatsu: It definitely runs I ran it. It’s a cross table like select * from a,b.

Varieur: Tum: use a proper CROSS JOIN declaration then

Shaud: I just want to compute the total and use it to compute the percentile for each row

Varieur: Tum: FROM a, b is an implicit join. Don’t use that either.

Varieur: Tum: yes, you can achieve this with a simple CROSS JOIN