Back to the month index |
Back to the list index
|
Jethro Wright (jetman@li.net)
Tue, 18 Nov 1997 17:52:33 -0500
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
- Next message: Marcantonio Magnarapa: "Re: Large text fields for msql"
- Previous message: Sol Katz: "Re: install problem"
- Next in thread: Marcantonio Magnarapa: "Re: Questions About mSQL 2.01 for Win32"
- Reply: Marcantonio Magnarapa: "Re: Questions About mSQL 2.01 for Win32"
Message-Id: <199711182302.SAA24880@linet06.li.net> From: "Jethro Wright" <jetman@li.net> Subject: Questions About mSQL 2.01 for Win32 Date: Tue, 18 Nov 1997 17:52:33 -0500
Folks: To get an idea about the port issues for bringing mSQL
2.03 into the Win32 world, I decided to give the 2.01 port a try. Well,
it kinda works. But I still have questions <sigh>:
1) When the daemon boots, it displays a message: 'Dynamic config
failed! Server can accept 2006 connections.' What does this mean ?
It isn't in the manual (specifically, manual.rtf. or manual.html.)
2) I did a dump of my mSQL 1.16 tables and brought them into my
new mSQL 2.01 server. Okay, that was easy, but then one the fields
appears to have gotten mangled. That is, I have a char(2) field,
which is to receive two char state names. When I do a simple SELECT
stmt (SELECT * FROM name_addr), the rows where the state fld has
data have an extraneous '{' appended to the data in the field. Every
other field seems to fine. More to follow on this one....
3) If I modify this query to add an ORDER BY clause to sort on the
lname field (ie. SELECT * FROM name_addr ORDER BY lname ASC), the
last 4 fields for _every_ record is either blank or NULL. I might
add that none of this happened w/ mSQL 1.16c.
Later, gang....Jet
- Next message: Marcantonio Magnarapa: "Re: Large text fields for msql"
- Previous message: Sol Katz: "Re: install problem"
- Next in thread: Marcantonio Magnarapa: "Re: Questions About mSQL 2.01 for Win32"
- Reply: Marcantonio Magnarapa: "Re: Questions About mSQL 2.01 for Win32"