-
When I run the command to create the crud from the migration, I get the following error and it is basically because the sql server does not have this command, is it possible to make a change?
Err…
-
### Environment
* Python version: 3.9
* Nautobot version: 2.0.x
* nautobot-device-onboarding version: 2.0.0 -> 2.0.2
```
nautobot@nautobot:~$ nautobot-server post_upgrade
Error in link c…
-
If you have a long-lived client object, the server can start complaining about the baton:
```
LibsqlError: SERVER_ERROR: Server returned HTTP status 400: Received an invalid baton
at (node_m…
-
As title suggest, these seems to be a bug when creating trigger on a table that doesn't exist yet and is part of the same migration. In such case autogenerated create fails with error.
Example defi…
-
## Bug Report
**For English only**, other languages will not accept.
Before report a bug, make sure you have:
- Searched open and closed [GitHub issues](https://github.com/apache/shardingsphe…
czywj updated
1 month ago
-
### Bug description
I want Prisma-governed schema to be in a different DB schema than the default `dbo`. However initialization step fails with an error message.
### How to reproduce
Generall…
-
### Feature Request
#DataMigration
-
When executing SQL migrations, the parser misses the semicolon and incorrectly merges statements if a string contains "--" after a space, mistakenly interpreting it as the start of a comment. This iss…
Ynng updated
6 months ago
-
### Bug description
Even with a very minimal schema.prisma, calling `findUnique()` on a PrismaClient() causes Node to run out of memory and crash.
### How to reproduce
0. I was able to intros…
-
### Problem
I wasn't able to find the sql server native attribute FILESTREAM when creating a varbinary(max) column. this is really necessary to me.
### Suggested solution
Maybe add a native databas…