Page 1 of 1
Product evaluation hassles
Posted: Wed 12 Jan 2005 17:41
by Guest
I posted a message yesterday about the lack of product documentation, and as a consequence, another message about not having a clue how to use shared memory connections.
While I understand that people on the dotnet MySQL mailing list don't reply because it's a free product, I'm puzzled that no one at CoreLab bothered with these messages since I'm evaluating their product and I won't be able to buy if I couldn't get it to work or read its docs.
I appreciate it if anyone from CoreLab answered those messages.
Re: Product evaluation hassles
Posted: Thu 13 Jan 2005 16:10
by Oleg
You can download trial version of MySQLDirect .NET and learn a documentation.
MySQLDirect .NET Trial is available for download at
http://www.crlab.com/mysqlnet/mysqlnet.msi
Shared memory access not working
Posted: Thu 13 Jan 2005 19:55
by Guest
The documentation says that the protocl connection string property should accept the values TCP, Pipe, and Memory. When the I specifiy "Protocol=Memory" in the connection string, I get:
Unhandled Exeption: Wrong or unknown protocol
This is a code snippet:
Code: Select all
MySqlConnection conn = new MySqlConnection("server=localhost;user id=myuid; password=mypwd; database=mydb; protocol=memory;");
MySqlCommand cmd = new MySqlCommand(String.Format("select * from sometable where rowno >= {0} limit {1}", startrow, pagesize), conn);
conn.Open();
MySqlDataReader rdr = cmd.ExecuteReader();
It's bombing on ExecuteReader(). If I remove "protocol=memory" from the connection string, it works fine.
Am I doing something wrong?
I really need to get that shared memory access working to avoid the overhead of the loopback TCP stack.
Thanks!
Re: Shared memory access not working
Posted: Fri 14 Jan 2005 09:15
by Oleg
This question has already been discussed in the forum.
Please see topic:
Shared Memory connections.