[puntloos]

Nah I found that feature.. but thanks! 🙂

And hmm yea multiple connects would sorta fix it..

Anyway.. SQLYog programmers actually reading this? Or are you hard at work implementing all my featurerequests? If not why not? 😛 – don't be a stranger now!

(oh and Merry Xmas etc.)

[puntloos]

Shadow> naw I didnt overlook THAT much, I am now a moderate PHP programmer so I'm aware of how to formulate SQL queries, Im just looking at this from an admin point of view. I'm the admin of a chat/mail site, and all I want (for christmas.. lala) is a 'GUI' for my database so I can also quickly change a few values here and there.

Thanks for your comments, I do think the 'recheck' function would be useful, however I see your point as well.. In my opinion sometimes you have to do things the ugly way 😛 I mean sure I could take my site offline every time I want to change some foulmouthed kid's user info, then edit, then put it up again, but just a quick recheck would be neat-o ™

[puntloos]

Oh, two more things I'd implement:

6/ Allowing people to sort by this, then sort by that, then..

So for example if I had a table with gender, email, nickname, age:

a/ click on gender: it puts all men and women together (a “1 <" appears next to 'gender') b/ click on age: sorts them by age (but keeps men/women together) (a “2 <" appears next to 'age') c/ click on age again: makes age sort descending instead of ascending (“2 >” next to age)

d/ click on age again: removes the sort by age and puts men/women in the order they appear in the DB (“2 >” disappears next to age)

7/ Make a tickable box “recheck DB before write” next to the 'Done' button, so before applying all changes I've made in my table editing session the program should check if the values haven't changed already, while I was busy. Of course you can't be sure the table doesnt change between the check and the write, but at least it'll be safER.

[Author]

Posts