On Fri, Mar 01, 2024 at 03:25:35PM -0500, Tom Lane wrote:
> No, what he showed was correct. I'm talking about a different facet
> of the problem:
> ...
> Even if that took account of the exchange rate, it'd not be great.
> But it doesn't; it's just the same digits reinterpreted with a new
>
On Fri, 2024-03-01 at 08:14 -0800, Adrian Klaver wrote:
> [pointers to the documentation]
I know. I was not searching for help with PostgreSQL,
I was trying to point out the surprising behavior of
"character" as a suggestion for the talk.
Yours,
Laurenz Albe
On Thu, Feb 29, 2024 at 05:51:11PM -0500, Tom Lane wrote:
> >> money is a fixed-point decimal value, the number of decimal
> >> places is locale determined. I’m not aware of any particular
> >> problems with that
> > You forget about the currency symbol dynamic. Like with time zones
> > the
On 3/1/24 01:18, Laurenz Albe wrote:
On Thu, 2024-02-29 at 13:38 -0800, Guyren Howe wrote:
what are the misconceptions, or where might I find them for myself?
In addition to what was already said:
My current understanding:
* character is fixed-length, blank-padded. Not sure when you’d
On Thu, 2024-02-29 at 13:38 -0800, Guyren Howe wrote:
> what are the misconceptions, or where might I find them for myself?
In addition to what was already said:
> My current understanding:
> * character is fixed-length, blank-padded. Not sure when you’d
>want that, but it seems clear. Is
On 2/29/24 14:47, Guyren Howe wrote:
What is worth saying about custom range types? What even would be a good use case? A range of
strings or ip address ranges, something like that, I suppose?
I wrote a blog post and an extension for an inetrange type. It's from 2016 so it might need some
On 29 Feb 2024, at 14:51, Tom Lane wrote:
>
>>> - time with time zone *does* store the time zone, but this isn’t
>>> actually useful and should be avoided (I’m not entirely sure why and the
>>> docs only gesture at the problems without stating them, IIRC)
>
>> No it doesn't store the time zone.
"David G. Johnston" writes:
> On Thu, Feb 29, 2024 at 2:38 PM Guyren Howe wrote:
>> My current understanding:
>>
>> - character is fixed-length, blank-padded. Not sure when you’d want
>> that, but it seems clear. Is the name just confusing?
> Character is not stored fixed length, it is stored
On 28 Feb 2024, at 17:08, Guyren Howe wrote:
>
> I am to talk about Postgres’s type system at PGConf:
>
> https://postgresconf.org/conferences/2024/program/proposals/postgres-s-type-system
>
> I picked the issue because I think it’s poorly understood, greatly
> under-discussed, and an
On Thu, Feb 29, 2024 at 2:38 PM Guyren Howe wrote:
> In case I’m not correct on the issues with these types, myself, what are
> the misconceptions, or where might I find them for myself?
>
> My current understanding:
>
>- character is fixed-length, blank-padded. Not sure when you’d want
>
On 2/29/24 1:38 PM, Guyren Howe wrote:
In case I’m not correct on the issues with these types, myself, what
are the misconceptions, or where might I find them for myself?
My current understanding:
* character is fixed-length, blank-padded. Not sure when you’d want
that, but it seems
In case I’m not correct on the issues with these types, myself, what are the
misconceptions, or where might I find them for myself?
My current understanding:
• character is fixed-length, blank-padded. Not sure when you’d want that, but
it seems clear. Is the name just confusing?
• timestamptz
On Thu, Feb 29, 2024 at 10:11:03AM +0100, Laurenz Albe wrote:
> It might be good to explain how "timestamp with time zone" works.
> That's often confusing for beginners, because it is different from
> other databases and arguably deviates from the SQL standard.
The most confusing part is the
On Wed, 2024-02-28 at 17:08 -0800, Guyren Howe wrote:
> I am to talk about Postgres’s type system at PGConf:
>
> https://postgresconf.org/conferences/2024/program/proposals/postgres-s-type-system
>
> I picked the issue because I think it’s poorly understood, greatly
> under-discussed, and an
I am to talk about Postgres’s type system at PGConf:
https://postgresconf.org/conferences/2024/program/proposals/postgres-s-type-system
I picked the issue because I think it’s poorly understood, greatly
under-discussed, and an excellent way to empower postgres users.
I am reasonably conversant
15 matches
Mail list logo
