-
**测试环境1**:
OS: CentOS6.7
mycat: 1.6/1.5
Infobright: infobright-4.0.7-0-x86_64-ice.rpm
**测试环境2**:
OS: windows7_64
mycat: 1.6-release (Eclipse源码调试)
Infobright: infob…
-
```
What steps will reproduce the problem?
1.Drop database by pyodbc
What is the expected output? What do you see instead?
Expect that SQL database to be dropped but it's not.
(Error:42000', '[42000]…
-
```
What steps will reproduce the problem?
1.Drop database by pyodbc
What is the expected output? What do you see instead?
Expect that SQL database to be dropped but it's not.
(Error:42000', '[42000]…
-
```
What steps will reproduce the problem?
1.Drop database by pyodbc
What is the expected output? What do you see instead?
Expect that SQL database to be dropped but it's not.
(Error:42000', '[42000]…
-
## Expected Behavior
The `django_migrations` table should live in database `geonode`?
Should this not read `--database=default` instead of `--database=datastore`?
https://github.com/GeoNode/…
-
I was following https://github.com/aio-libs/aiomysql/blob/master/docs/sa.rst and I noticed that running the example multiple times did not work as expected.
The example:
```
import asyncio
impor…
-
```
What steps will reproduce the problem?
1. Attempt to connect to incorrect server name or instance using following code:
pyodbc.connect('DRIVER={SQL Server};SERVER=\\servername\inst01;', timeout=10…
-
```
What steps will reproduce the problem?
1. Attempt to connect to incorrect server name or instance using following code:
pyodbc.connect('DRIVER={SQL Server};SERVER=\\servername\inst01;', timeout=10…
-
```
What steps will reproduce the problem?
1. Attempt to connect to incorrect server name or instance using following code:
pyodbc.connect('DRIVER={SQL Server};SERVER=\\servername\inst01;', timeout=10…
-
We are currently using the feeder 1.7 implementation and we are suffering data loss when the feeder is connected to a master node and no data node is reachable. If the data node can't be reached withi…