[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Names for database access functions
- From: Dirk Laurie <dirk.laurie@...>
- Date: Thu, 18 Jun 2015 11:07:56 +0200
2015-06-17 23:43 GMT+02:00 Geoff Leyland <geoff_leyland@fastmail.fm>:
> What should each of these functions be called? The database binding
> I use frequently that actually offers a “rows" iterator [1] calls them:
> - “rows” for the array case that I don’t really use
> - “nrows” for the table case (I guess that stands for “named rows”?)
> - “urows” for the multiple return case (I’m not sure what the u stands for)
>
> Can anyone suggest a better naming convention?
If the above naming convention is used by a commonly available,
well documented module, the decision has been taken out of your
hands. Anything else, despite equally good documentation on your
part, would just be confusing, no matter how much better it is.
Your darmstadtium is my ununnilium :-)