Hello:
You do need to use Sync rather than Flush to create transaction
boundaries and error restart points. I suspect your problem was coming
from having only a Flush and not a Sync between the CREATE DATABASE and
the *prior* command.
Huummm there are no prior executed commands, the CREATE DATA
Carlos Guzman Alvarez <[EMAIL PROTECTED]> writes:
> Hello:
>>> No, it should just work. Can you give a test case? Do you see similar
>>> problems with other utility commands, or is it only CREATE DATABASE?
> I have made a litlle test more and i have it working now, i have made
> change for send
Hello:
> No, it should just work. Can you give a test case? Do you see similar
> problems with other utility commands, or is it only CREATE DATABASE?
I have made a litlle test more and i have it working now, i have made
change for send a Sync message instead of a Flush message after execute
th
Hello:
No, it should just work. Can you give a test case? Do you see similar
problems with other utility commands, or is it only CREATE DATABASE?
I have a litlle test more and i have it working now, i have made change
for send a Sync message instead of a Flush message after execute the
comma
Carlos Guzman Alvarez <[EMAIL PROTECTED]> writes:
> I'm trying to create a database using the extended query mode ( with my
> own implementation of the 3.0 protocol in C# ) but i'm having problem,
> the CREATE DATABASE command seems to be executed well and the answer of
> the server is the expec
Hello:
I'm trying to create a database using the extended query mode ( with my
own implementation of the 3.0 protocol in C# ) but i'm having problem,
the CREATE DATABASE command seems to be executed well and the answer of
the server is the expected but the database is never created, if i exec
