Solving the symbol-vs-number conundrum
Lassi Kortela
(09 Aug 2020 21:29 UTC)
|
Re: Solving the symbol-vs-number conundrum
John Cowan
(10 Aug 2020 01:02 UTC)
|
Re: Solving the symbol-vs-number conundrum
Lassi Kortela
(10 Aug 2020 06:48 UTC)
|
SQLSTATE
Lassi Kortela
(10 Aug 2020 07:03 UTC)
|
Any alphanumeric errors anywhere?
Lassi Kortela
(10 Aug 2020 07:11 UTC)
|
Re: Any alphanumeric errors anywhere?
Lassi Kortela
(10 Aug 2020 07:15 UTC)
|
Re: Any alphanumeric errors anywhere?
Göran Weinholt
(10 Aug 2020 07:44 UTC)
|
VMS errors
Lassi Kortela
(10 Aug 2020 08:29 UTC)
|
Re: VMS errors
John Cowan
(11 Aug 2020 02:44 UTC)
|
Re: Solving the symbol-vs-number conundrum
John Cowan
(10 Aug 2020 20:36 UTC)
|
Re: Solving the symbol-vs-number conundrum
Lassi Kortela
(10 Aug 2020 21:30 UTC)
|
Re: Solving the symbol-vs-number conundrum
John Cowan
(11 Aug 2020 03:48 UTC)
|
Re: Solving the symbol-vs-number conundrum
Lassi Kortela
(11 Aug 2020 06:50 UTC)
|
Re: Solving the symbol-vs-number conundrum
hga@xxxxxx
(12 Aug 2020 12:01 UTC)
|
Re: Solving the symbol-vs-number conundrum
John Cowan
(12 Aug 2020 12:48 UTC)
|
Semantic property names and static vs dynamic types
Lassi Kortela
(14 Aug 2020 15:54 UTC)
|
Re: Semantic property names and static vs dynamic types
John Cowan
(14 Aug 2020 22:06 UTC)
|
Re: Solving the symbol-vs-number conundrum
hga@xxxxxx
(12 Aug 2020 12:06 UTC)
|
Re: Solving the symbol-vs-number conundrum Lassi Kortela (14 Aug 2020 15:57 UTC)
|
Re: Solving the symbol-vs-number conundrum
hga@xxxxxx
(15 Aug 2020 16:26 UTC)
|
Re: Solving the symbol-vs-number conundrum
hga@xxxxxx
(10 Aug 2020 22:11 UTC)
|
>> category >> class-code >> class-title >> subclass-code >> Subclass-title >> >> All these things are determined by the SQLSTATE, so I don't see much >> reason for lugging them around in status objects. > > I say leave it at the discretion of the library developer, and for now > many of them are used in one SRFI example. Lugging them around may save > the end user a trip to a file or book. OK, let's put them in the registry but make them strictly optional. A particularly conscientious database driver programmer can fill them in. Well, class-code and subclass-code are simple parts of sqlstate so maybe they shouldn't be there? We can decide once we're actually writing drivers, SRFI 198 doesn't need to talk about SQL stuff. > OK, I'm particularly bad at spelling, but John is absolutely > right, mnemonic is /horrible/ for natives English speakers trying to > consistently spell it correctly. :D OK, point well made! Mnemonic is out.