Which RCS is the best James Blunt?
-
As none of these you pointed have hair, Stallman is the least bald.
-
I've used both HeidiSQL and SQLYog (not free but ~$60US) for MySQL.
-
Aaaaaaand, she's back.
For now.
-
I've been around. I can't keep up most of the time.
-
It was more a comment that in the year you have been here, you have only made a handful of posts.
Lurker.
-
Very much a lurker. Even was around for the old forums (though never registered).
But I spend enough time here that I use memes at home. And this is totally derailing this thread.
-
And this is totally derailing this thread.
That's nothing new. IIRC the thread's title was originally "Which RDBMS is the least bad?" or something like that.
Filed under:
TopicTitle drift
-
And this is totally derailing this thread.
That's nothing new. IIRC the thread's title was originally "Which RDBMS is the least bad?" or something like that.
I know...I just didn't think my lurking was very interesting.
On topic: I use MS SQL Server at work, I have used Express at home, and of course, MySQL.
In previous positions I have used Oracle.I like MS SQL Server but it is overkill for anything I do on my own and since I am already familiar with MySQL it is just easier to use.
-
It's scary to think there maybe many lurkers reading lame stuff I write
edit: small font, so the lurkers don't see it
-
It's scary to think there maybe many lurkers reading lame stuff I write
If they're lurking fast enough to see it before you delete it.
-
I know...I just didn't think my lurking was very interesting.
It is if your avatar is accurate.
-
-
Stallman doesn't seem to be balding; he's definitely a hippie.
-
-
Discourse isn't handling the small tags
-
Discourse isn't handling the small tagsFor a short while the first line was small and the second line was normal size...figure that one out.
-
Discourse isn't handling the small tagsYes it is...
<div style="display: block;" class="cooked"> <p><small><small> </small></small></p><p>It's scary to think there maybe many lurkers reading lame stuff I write</p> <p>edit: small font, so the lurkers don't see it</p> <p></p> <!--​--> <!--​--> </div>
-
Looks normal from here!
I change my mind when I said I didn't care about Discourse bugs, this is annoying.
-
It was small for a few seconds then it wasn't.
Discoursistanty! <-- does this count as an @accalia
-
I change my mind when I said I didn't care about Discourse bugs, this is annoying.
The Discourse Syndrome is passing. Soon you will be yelling at your computer and cursing @wood's name.
-
Cooked ≠Preview. Discoursistency! Does it really surprise you that the editor isn't WYSIWYG?
-
Change it to
<small>It's scary to think there maybe many lurkers reading lame stuff I write</small> <small>edit: small font, so the lurkers don't see it</small>It's scary to think there maybe many lurkers reading lame stuff I write
edit: small font, so the lurkers don't see it
-
I know...I just didn't think my lurking was very interesting.
It is if your avatar is accurate.
Yeah, I have since cut my hair, changed its color, and bought new glasses.
-
It was small for a few seconds then it wasn't.
Discoursistanty!Just a ninja edit, really.
-
This thread has been going for this long and no one has been pedantic enough to point out MySQL is so last season and everyone moved to MariaDB because of Oracle?
-
According to internet wisdom, there are about 10x as many lurkers as active users.
Let's see, including me, 5 people have liked or replied to that post, so 50 people would be the lower estimate on the number of lurkers who have read it (maybe Discourse knows the exact number?).
-
Also, no one has mentioned APDB yet.
-
My post originally said MySQL/Maria
But I've never used Maria so it got culled.for pedantry.
-
-
You're better off not tinkering with it.
From my experience, SQL Server is pretty good at managing its own memory if you leave it alone, even with other apps running on the same box. I've seen more than one SQL Server have major performance problems not because the defaults were bad, but because the admins tinkered with all sorts of shit to justify their paychecks.
I did have to lower it on a box with 4 instances. 3 were running dog-slow and the other had commandeered a good 80% of the available memory. The speed was fine on all of them after telling the greedy one it could only have 4GB. So multiple instances might still be a special case unless I hit a memory management bug (SQL Server 2008 R2).
-
WYSIWYG
WYSIWY HEH you wish.
On topic: I use MySQL - works fine for me. But my stuff is usually insanely small-data, so....
Also, MySQL workbench. Forget that PHPMyAdmin crap.
-
On topic: I use MySQL
MySQL is not software libre, obviously that does not belong here (nor does it belong on your computer as it bastardizes your freedoms) and it is therefore off-topic.
-
*checks pockets*
I know I have one here somewhere... I... No? Damn. Well it looks like I'm all out of fucks to give. I am so, so sorry...
Really though, I don't care, I just want my stuff to work.
-
Oh yeah I guess I should clarify I've only ever done one instance per piece of hardware.
-
I have experience with:
-
MS SQL Server
Pretty damn good. Capable. Performant. Best GUI tooling of all the databases. Good integration with .NET, so in that realm, it's pretty much a must.Downsides: Price. Windows only. Not very POSIX compliant. That is, they have all sorts of capabilities, but always wrapped in their own special little syntax. So it's harder to get into the platform, and once in, hard to get out.
-
MySQL
Once you configure it properly, it's a pretty stable, well tested solution. Plenty of info and help online. Dead simple to set up on any machine under the sun. GUI support is pretty good, not on level of MS, but very capable nonetheless.On the downside: this. Also, Oracle. Also, it's starting to seriously lag behind in terms of features. MariaDB mitigates some of these, but not all.
-
PostgreSQL
Great DBMS and getting better all the time. Very active development, they are usually the first ones to bring in new features. You won't find a more complete solution for free (and maybe even among the paid ones, I don't know, I haven't used Oracle).On the downside, GUI support is terrible, and doesn't seem to be getting better at all. Some of the database features feel clumsy (eg. vacuum-ing, slow COUNT). Also, support is based on a fucking mailing list. But these complaints are probably due to me using this DB much harder than any of the others.
-
Redis
Fast. Reliable. Pub/sub support. It's a great "glue" for any project. If you need a cache, a message broker, a key-value store and/or a distributed queue, you can just add Redis and it will fill in any or all of these roles.On the downside, it's a RAM hog. You'll need the
size_of_data x 2MB-s of RAM for it to function normally. Others report partitioning problems, but I haven't used that. -
InfluxDB
See here: https://what.thedailywtf.com/t/influxdb-improvements/52217 -
SQLite
A replacement for writing data into a file using your own format. Nothing more, nothing less. Seems to be working well for its intended purpose.
I played around with others (MongoDB, CoachDB, Riak), but I don't have them running in any kind of production, so they don't count.
-
-
In technology, I have learned that searching people opinion doesn't help much. In my anedoctal experiences, the best correlation with not geting screwed by a technology choice is popularity.
Impopular tech frequently have a good reason to be impopular. See php, despite all criticism, it still is the most used, and took me a long time to figure the difference in memory usage between php and ruby. I learned it by installing Discourse, and trying to learn why it requires all that memory.
Then you have postgresql and mysql. Postresql has better features, but people use mysql not only because it have better gui tools, but it also consume less resources if you have hunders of small databases in a server, as is the case with cheap hosting providers. That helps getting the hosting cost of mysql down, and is probably a great part of most commodity applications using it.
And then there is mysql cluster, that is different than the normal mysql, that is something between sql and nosql databases. There is probably a reason facebook is using it.
-
took me a long time to figure the difference in memory usage between php and ruby
The core of Ruby might or might not be particularly well-written, but many of the libraries for it including the standard ones for server-side interfacing with the web are written with the assumption that there's vast amounts of memory and that doing a
fork()is nearly free. And now they're stuck with all that shit, because those abstractions leak, no matter how much they try to hide them.I really dislike working with Ruby (well, Rails) code. There's just so many subtle things wrong.
-
On the downside, GUI support is terrible, and doesn't seem to be getting better at all. Some of the database features feel clumsy (eg. vacuum-ing, slow COUNT). Also, support is based on a fucking mailing list. But these complaints are probably due to me using this DB much harder than any of the others.
I never, ever in my life needed a single GUI management tool. No one can ever predict what monstrous query I might conceive involving these handy pg_* tables. Shelling $$$ for something like Navicat which has bells and whistles, but at the same time is inherently dumber than me and constraining me? What am I, a database masochist?
I wonder how the Instagram guys cope. No. GUI. Management. Tools. DREADFUL!!
Or maybe they just don't hire whiners who can't do shit without hand-holding and mouse-clicking.
(May I add that there was a discussion about having a bug database proper. The consensus was that the mailing list Just Works as is.)
-
I never, ever in my life needed a single GUI management tool. No one can ever predict what monstrous query I might conceive involving these handy pg_* tables. Shelling $$$ for something like Navicat which has bells and whistles, but at the same time is inherently dumber than me and constraining me? What am I, a database masochist?
I wonder how the Instagram guys cope. No. GUI. Management. Tools. DREADFUL!!
Or maybe they just don't hire whiners who can't do shit without hand-holding and mouse-clicking.
Oh? I suppose you print out schemas on a piece of paper and tape it next to the screen, so you can track which columns you have?
Also, type in SQL queries every few seconds, to monitor the traffic?
Sure, you can script all of these, but I aint got time for that, need to get real work done (by posting this on TDWTF).
(May I add that there was a discussion about having a bug database proper. The consensus was that the mailing list Just Works as is.)
Yeah, you don't want Stallman types, who read their emails using
catagainst the raw database, to be inconvenienced too much.
-
Oh? I suppose you print out schemas on a piece of paper and tape it next to the screen, so you can track which columns you have?
I have enough short term memory for this, and can into \d and information_schema.
Also, type in SQL queries every few seconds, to monitor the traffic?
Scripting. Ever heard of it?
Also, type in SQL queries every few seconds, to monitor the traffic?
psql supports history, for one. Also, you won't have the time to do real work if you need to stare at the traffic in real time. I'd just script something that kicks me in the ass when things get unusual enough.
Sure, you can script all of these, but I aint got time for that, need to get real work done
I'd fire a person saying shit like that for being first degree inefficient, and being not proactive enough to improve the tools. Or are you the guy from that company where they straight away prohibit scripting for exactly the inverse policy? I remember reading something like this in Featured Articles a while ago.
-
Yeah, you don't want Stallman types, who read their emails using cat against the raw database, to be inconvenienced too much.
It just so happens that these types implement and fix the most of the shit.
When in Rome, do as Romans do...
-
I'd fire a person saying shit like that for being first degree inefficient, and being not proactive enough to improve the tools.
Sorry, not enough time. I just started a new project, and am too busy coding a PHP IDE to use for it. Maybe once that and my git-based issue tracker are ready, I can get on with reinventing database tooling as well.
-
git-based issue tracker
That's actually potentially a Good Idea, as long as you use the records in git to populate a database for ease of display.
-
Sorry, not enough time. I just started a new project, and am too busy coding a PHP IDE to use for it.
Not worth it unless it writes all the code for you on full auto. Text editors are there, extensible any way you want. ;-)
-
You, sir, are WRONG.
<insert Gene Wilder/Willy Wonka yelling at Charlie meme><not really dickweedy, but suitably pendantic>MySQL was always dual licensed, back even in the MySQL AB days because that was how they funded the damn thing before Sun bought them and before Oracle ate Sun.
It's also why PHP had to rewrite its MySQL client connector from scratch a while back after PHP stopped being GPL itself.
-
It was actually slightly different than what you said. (And I'm wrong too)
With reference to MySQL 3.23.6 linked above, basically, for non-Microsoft OSs, if you don't directly include it as part of your package, and you don't charge fee for installation/maintenance of the database system, you can use it for free. If any of the "don't" applied to you, you need to pay for license.
For use in Microsoft OSs (except educational use or government sponsored research), you need to pay for license after 30 days.
-
ERR_OUTDATED_REFERENCE
Get documentation from this century, will ya?
-
He point out my description for licensing terms before dual license is wrong, so I have search for earlier version.
-
before Oracle ate Sun.
...aw, you mean Sun the company, don't ya? I was kind of hoping...
-
If you're talking about how things were in the past, use past tense in your writing.
