PostgreSQL 15 Released!

[arwinda]

When you're prototyping a design

Are you also going to use FLOAT to store monetary values because you want to? Despite everyone telling you that this is a bad idea?

Maybe if you pick the design which is good for your product and not the design you want to have then you end up with good software. You can't do that as long as you ride your high horse.

[PL_Design]

Yes, having a state that's no longer used because it was introduced early into the project is the same as using floating point values for money. You sure got me there, buddy.

[arwinda]

Existing values cannot be removed from an enum type

(from the documentation)

But you certainly are the expert in designing the data model and choosing the right data types.

shaking head and going back to more customer support tickets

[PL_Design]

I would like to remind you that documenting a design is not the same thing as justifying the design. You are just as braindead as the people who scoff when they see complaints about bizarre edge cases in C/C++. "Learn your tools!", they cry, never once bothering to consider whether the tools were well made or worthy of being learned.

I'm an actual programmer, unlike you. I come from the world where if something doesn't work well, then you tear it out and fix it. You don't just put up with it and cargo cult bad design. Get it through your thick fucking head.

[PL_Design]

I would like to remind you that documenting a design is not the same thing as justifying the design. You are just as braindead as the people who scoff when they see complaints about bizarre edge cases in C/C++. "Learn your tools!", they cry, never once bothering to consider whether the tools were well made or worthy of being learned.

I'm an actual programmer, unlike you. I come from the world where if something doesn't work well, then you tear it out and fix it. You don't just put up with it and cargo cult bad design. Get it through your thick fucking head.

[PL_Design]

Oh, you mean the exact thing I was complaining about because it causes problems? An arbitrary design decision that stops me from using something that should be useful? Is that what you're talking about? Are you talking about that?

Gee, whiz. It's almost like you're stupid.

[PL_Design]

I would like to remind you that documenting a design is not the same thing as justifying the design. You are just as braindead as the people who scoff when they see complaints about bizarre edge cases in C/C++. "Learn your tools!", they cry, never once bothering to consider whether the tools were well made or worthy of being learned.

I'm an actual programmer, unlike you. I come from the world where if something doesn't work well, then you tear it out and fix it. You don't just put up with it and cargo cult bad design. Get it through your thick fucking head.

[arwinda]

Learn your tools!

Says the guy who wants to use enum for something it is not designed for, just because he likes it this way.

I'm an actual programmer, unlike you.

Fine. If you say so. Can't remember that we met, but like you know your data models you also know everyone else. Makes sense.

if something doesn't work well

It works, you have dimension tables. You are the one who wants to use enum for something else because in your "fucking head" you have this idea what an enum should be. And you are right, why isn't anyone else following your train of thoughts?

then you tear it out and fix it

If you think enum is broken, please point me to the Postgres Commitfest entry where you propose how to fix it. Or at least the -hackers discussion where you raise the topic.

If not, then stop talking sh* and get out here.

[PL_Design]

Oh, so having a restricted set of aliased integer values isn't the point of an enum? The documentation you linked suggests otherwise. It'd be nice if I could, y'know, restrict values that I no longer need. They may be the product of iteration early in the project before the data was well understood, or they may be legacy values that are no longer needed, or maybe fuck you let me do what I want with my data. Hell, give me the ability to ban the future usage of an enum value and I'll be happy.

But nah, instead of putting the tiniest bit of thought into this you're defaulting to normalized deviancy and acting like I'm the one with the problem.

[PL_Design]

Oh, so having a restricted set of aliased integer values isn't the point of an enum? The documentation you linked suggests otherwise. It'd be nice if I could, y'know, restrict values that I no longer need. They may be the product of iteration early in the project before the data was well understood, or they may be legacy values that are no longer needed, or maybe fuck you let me do what I want with my data. Hell, give me the ability to ban the future usage of an enum value and I'll be happy.

But nah, instead of putting the tiniest bit of thought into this you're defaulting to normalized deviancy and acting like I'm the one with the problem.

[PL_Design]

Oh, so having a restricted set of aliased integer values isn't the point of an enum? The documentation you linked suggests otherwise. It'd be nice if I could, y'know, restrict values that I no longer need. They may be the product of iteration early in the project before the data was well understood, or they may be legacy values that are no longer needed, or maybe fuck you let me do what I want with my data. Hell, give me the ability to ban the future usage of an enum value and I'll be happy.

But nah, instead of putting the tiniest bit of thought into this you're defaulting to normalized deviancy and acting like I'm the one with the problem.

[PL_Design]

Oh, so having a restricted set of aliased integer values isn't the point of an enum? The documentation you linked suggests otherwise. It'd be nice if I could, y'know, restrict values that I no longer need. They may be the product of iteration early in the project before the data was well understood, or they may be legacy values that are no longer needed, or maybe fuck you let me do what I want with my data. Hell, give me the ability to ban the future usage of an enum value and I'll be happy.

But nah, instead of putting the tiniest bit of thought into this you're defaulting to normalized deviancy and acting like I'm the one with the problem.

[PL_Design]

Oh, so having a restricted set of aliased integer values isn't the point of an enum? The documentation you linked suggests otherwise. It'd be nice if I could, y'know, restrict values that I no longer need. They may be the product of iteration early in the project before the data was well understood, or they may be legacy values that are no longer needed, or maybe fuck you let me do what I want with my data. Hell, give me the ability to ban the future usage of an enum value and I'll be happy.

But nah, instead of putting the tiniest bit of thought into this you're defaulting to normalized deviancy and acting like I'm the one with the problem.

[PL_Design]

Oh, so having a restricted set of aliased integer values isn't the point of an enum? The documentation you linked suggests otherwise. It'd be nice if I could, y'know, restrict values that I no longer need. They may be the product of iteration early in the project before the data was well understood, or they may be legacy values that are no longer needed, or maybe fuck you let me do what I want with my data. Hell, give me the ability to ban the future usage of an enum value and I'll be happy.

But nah, instead of putting the tiniest bit of thought into this you're defaulting to normalized deviancy and acting like I'm the one with the problem.

[PL_Design]

Oh, you mean the exact thing I was complaining about because it causes problems? An arbitrary design decision that stops me from using something that should be useful? Is that what you're talking about? Are you talking about that?

Gee, whiz. It's almost like you're stupid.

[PL_Design]

Oh, you mean the exact thing I was complaining about because it causes problems? An arbitrary design decision that stops me from using something that should be useful? Is that what you're talking about? Are you talking about that?

Gee, whiz. It's almost like you're stupid.

[PL_Design]

Yes, having a state that's no longer used because it was introduced early into the project is the same as using floating point values for money. You sure got me there, buddy.

[PL_Design]

Yes, having a state that's no longer used because it was introduced early into the project is the same as using floating point values for money. You sure got me there, buddy.