Should we fix this or document it somewhere? It is the issue of pg_get_serial_sequence handling upper/lower case differently for its two arguments, if I remember correctly.
--------------------------------------------------------------------------- Christopher Kings-Lynne wrote: > > Right. From a bare-functionality point of view there's nothing wrong > > with it, it just seems inconsistent and therefore likely to trip someone > > up in future. > > > > But it seems no one else cares, so I'll shut up about it ... > > I'm happy to have it fixed or changed :) I was just pointing out why it > was like it is. It uses two different parsing functions. > > Chris > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to [EMAIL PROTECTED] so that your > message can get through to the mailing list cleanly > -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
