Re: renaming ExecStoreWhateverTuple
| От | Alvaro Herrera |
|---|---|
| Тема | Re: renaming ExecStoreWhateverTuple |
| Дата | |
| Msg-id | 20190325152751.GA15490@alvherre.pgsql обсуждение исходный текст |
| Ответ на | renaming ExecStoreWhateverTuple (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: renaming ExecStoreWhateverTuple
|
| Список | pgsql-hackers |
I agree about taking out the "Exec" part of the name. On 2019-Mar-25, Robert Haas wrote: > I'm not sure exactly what names would be better. Perhaps just change > the "Exec" prefix to "Slot", e.g. SlotStoreHeapTuple(). Or maybe put > InSlot at the end, like StoreHeapTupleInSlot(). Or just take those > four words - slot, heap, tuple, and store - and put them in any order > you like. TupleSlotStoreHeap? HeapStoreTupleInSlot? (I wonder why not "Put" instead of "Store".) Should we keep ExecStoreTuple as a compatibility macro for third party code? -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: