?

Log in

The cat is back. - The Desian Universe
Links Home / GitHub January 2017
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
 
 
 
deskitty
deskitty
Des
Mon, Mar. 10th, 2003 07:04 pm
The cat is back.

My friendly neighborhood cat paid me another visit today...I hadn't seen him for several weeks. S/he is cute, even when sprinting off into the bushes to get away from the Jeep (which would just loooove so much to eat him...) :p

I got pissed in 205 today, and started ranting in the general direction of one of my teammates about how the class is so poorly organized, and whatnot. Of course, I don't really have much room to complain here...I have far too many late points on my homework than I'd like. :(

I've been playing with PostgreSQL, and lemme tell ya, table inheritance and OIDs make me feel all warm and squishy inside...it's sooooo much cooler than having to worry about autogenerated IDs and (only half-existent) foreign keys with MySQL. Now I just say "inherits (whatever)", and boom, my lower-level table has all the fields it needs, so there's none of this one-to-one BS that most other RDBMSs do. :)

I'm hungry, and I have absolutely no idea what I'm going to do for dinner. I have leftover green beans in the refrigerator, and I had some idea about what I wanted to do with them, but then I forgot. Hmm. :(

-- Des

Current Mood: hungry hungry
Current Music: "Avenue" by Paul Van Dyk ( Massinova)

6CommentReplyShare

xenithtoast
xenithtoast
Xenith
Mon, Mar. 10th, 2003 08:41 pm (UTC)
Dis one, or dat one?

Cripes. I can never decide between MySQL and PostgreSQL for my work. When you're writing something that is going to be made public, you need to use something that everyone has. (MySQL) When you want good stuff, you can't use what everyone has, but not everyone has the good stuff. (PostgreSQL)

And I'm using the term "everyone" a tad loosely. ;-)


ReplyThread
xenithtoast
xenithtoast
Xenith
Mon, Mar. 10th, 2003 08:46 pm (UTC)
Re: Dis one, or dat one?

And if you look *reeeeeeal* close, you can see where I stopped typing to play another round of Counter-Strike. ;-)


ReplyThread Parent
deskitty
deskitty
Des
Mon, Mar. 10th, 2003 08:49 pm (UTC)
Re: Dis one, or dat one?

Actually, it's more of a speed/features tradeoff...IIRC MySQL is faster than Post, even though Post offers more features (like ACID transactions and OO tables). If people don't have Postgres, and whatever I'm writing happens to use it, there's probably a damn good reason for it. So they can just install Postgres and deal, thank you very much. :P

Although IMO Postgres still has a few things that need to be worked out. One of which is propagation of indexes and foreign keys to derived tables. Although, I hear they're working on fixing that in a future release.

The whole "VACUUM nightly" thing is kinda annoying, too. Although, it only took me 5 minutes to get the cron script setup.


ReplyThread Parent
xenithtoast
xenithtoast
Xenith
Mon, Mar. 10th, 2003 09:09 pm (UTC)
Re: Dis one, or dat one?

Only problem is that a lot of people don't have the leisure to install stuff like that. You'll get an admin who will say "MySQL is good enough for you, and that's all you're gonna get!"


ReplyThread Parent
devpreed
preed
Mon, Mar. 10th, 2003 09:46 pm (UTC)
Re: Dis one, or dat one?

That whole "MySQL is faster than Postgres" thing is really a myth. It's based upon old versions of Postgres and MySQL; since then, Postgres has gotten faster and MySQL has gotten slower if you actually use any of the features that make it less Access-like.

That statement is also usually parroted by people who don't know how to write SQL; this is a great example of that.

Also, you don't need to VACUUM with 7.2 or higher; it does that in real-time, automatically (actually, there's a "vacuuming" thread that runs all the time and takes care of it.

But yeah... Postgres is nice; it makes you feel like you're using a real database again. My only complaint is that it's very difficult to change table definitions while the database is in play. I've heard they're working on this for 7.4, and really... I don't blame them. It's so easy in MySQL because they don't give a shit about data integrity, so they don't care if you lop off a field that has a required foreign key. MySQL has no concept of foreign keys.

Postgres isn't 100% ACID, but it's the closest open source thing you'll find.


ReplyThread Parent
deskitty
deskitty
Des
Mon, Mar. 10th, 2003 10:03 pm (UTC)
Re: Dis one, or dat one?

That whole "MySQL is faster than Postgres" thing is really a myth. It's based upon old versions of Postgres and MySQL; since then, Postgres has gotten faster and MySQL has gotten slower if you actually use any of the features that make it less Access-like.

Last I heard (several months ago), My was faster for simpler queries, but Post was faster for complex ones...although I don't know. It's been a while since I actually went through and proactively researched the benchmarks. I don't consider it all that important, since Post is more featureful anyway. I suspect that everything on deneb will migrate to Post, eventually, but I don't know it well enough yet to do that.

That statement is also usually parroted by people who don't know how to write SQL; this is a great example of that.

True...and one of the reasons I want to completely switch is that My's bastardized version of SQL gives me a headache. :) Besides, I just think table inheritance and OIDs are cool.

Also, you don't need to VACUUM with 7.2 or higher; it does that in real-time, automatically (actually, there's a "vacuuming" thread that runs all the time and takes care of it.

According to the 7.3 docs, you still need it. When I do a ps, I'm only seeing one postmaster thread, and two stats threads.

But yeah... Postgres is nice; it makes you feel like you're using a real database again. My only complaint is that it's very difficult to change table definitions while the database is in play.

Amen to that. ;) But how is it more difficult in Post than it is in My? Is it just because of indexes/foreign keys? Cause I've been doing plenty of ALTER TABLEs (admittedly on blank ones), and haven't had any problems thus far.

Postgres isn't 100% ACID, but it's the closest open source thing you'll find.

It isn't? Hmm...I'm probably misremembering something then. Not that I care that much for what I'm doing (playing around).


ReplyThread Parent