orm
Here are 2,546 public repositories matching this topic...
Issue type:
[ ] question
[ ] bug report
[ ] feature request
[x] documentation issue
Steps to reproduce or a small repository showing the problem:
- Open
Getting started(https://typeorm.io/#/) in documentation - Hover the anchors and it will be marked as the examples below with undefined
https://typeorm.io/#undefined/quick-start`https://typeorm.io/#/undefined/ins
Describe the bug
When the elevated database user account does not have permission to create a schema, it cannot establish a connection with an existing database.
But when I provided the root account, I successfully established a connection with the database, but prisma created a schema called prisma.
Look like this:
 can
-
Updated
May 5, 2020 - Java
This is a:
-
enhancement
-
CakePHP Version: any (collections).
Since you have already used psalm and it's templates feature, I would like to suggest you to type all the collections library
-
Updated
Mar 30, 2020 - Python
In the documentation (https://github.com/coscms/xorm/blob/master/docs/QuickStart.md > Section 1: Create ORM Engine > 1.Logs)
I saw that there was/is an engine.ShowError = true. However the ShowError is not an attribute / method anymore. Also I don't find it anywhere in the code.
Did this dissapear? If so, why? And could you bring it back?
Other than that, really enjoying the library. Bi
In the tutorial events there is this example:
const User = bookshelf.model('User', {
tableName: 'users',
initialize() {
this.on('saving', (model) => {
return User.forge({email: model.get('email')}).fetch().then((user) => {
if (user)
throw new Error('That email address already exists')
Given that we support CURRENT_TIMESTAMP, the lack of CURRENT_DATE feels like an omission. While you can hack it with date(now), I keep finding myself wishing there was a direct way to reference this. Given that now means CURRENT_TIMESTAMP, I think there's precedent for today meaning CURRENT_DATE. This is supported by all backends we support (and is in the ISO standard I believe).
use static analyzer
Use static analyzer
Variants:
https://github.com/phpstan/phpstan
https://github.com/vimeo/psalm
I found an issue for support of LocalDate, JetBrains/Exposed#100 but nobody asked for a time support.
https://www.postgresql.org/docs/9.1/datatype-datetime.html#DATATYPE-DATETIME-TABLE
Obviously, time can be stored with timestamp type, but I think it would be nice to have time column type.
-
Updated
May 5, 2020 - TSQL
-
Updated
May 5, 2020 - Rust
I've been accessing my other database just fine using db_alias for most collections that do not contain FileField() or ImageField() fields. However, for collections with FileField() or ImageField() I have not been able to access the file in the other database. Does db_alias not properly link fs.files and fs.chunks in the other database? Must one somehow add `meta = {"db_alias": "OtherDB"
It looks like renovate is compatible with pnpm!
Dependabot doesn't support pnpm see dependabot/dependabot-core#1736
what is prefer way to add relation and remove relation? I found example as below, but I did't find any document about the two methods.
case 'ADD_AUTHOR_TO_BOOK':
Book.withId(action.payload.bookId).authors.add(action.payload.author); // add new entity , add relation? this doesn't work.
break;
case 'REMOVE_AUTHOR_FROM_BOOK':
Book.withId(action.payload.bo
-
Updated
May 5, 2020 - Ruby
-
Updated
May 4, 2020 - Go
Improve this page
Add a description, image, and links to the orm topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the orm topic, visit your repo's landing page and select "manage topics."
Issue Description
Is your feature request related to a problem? Please describe.
When doing some migrations, I would like to delete a column created in a previous migration.
However, this is not possible with the current code for some scenarios.
An example :
migration v3