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

'use strict';

let opts = {tableName: 'Exercises'};

module.exports = {
    up: (queryInterf

Issue type:

[ ] question
[ ] bug report
[ ] feature request
[x] documentation issue

Database system/driver:

[ ] cordova
[ ] mongodb
[ ] mssql
[ ] mysql / mariadb
[ ] oracle
[x] postgres
[ ] cockroachdb
[ ] sqlite
[ ] sqljs
[ ] react-native
[ ] expo

TypeORM version:

[x] latest
[ ] @next
[ ] 0.x.x (or put your version here)

followed the docs for has manyhttp://gorm.io/docs/has_many.html for sqlilite

package main

import (
	"fmt"

	"github.com/jinzhu/gorm"
	_ "github.com/mattn/go-sqlite3"
)


type User struct {
	Id          string
	Name        string
	CreditCards []CreditCard `gorm:"FOREIGNKEY:user_id;ASSOCIATION_FOREIGNKEY:id"`
}

type CreditCard struct {
	Id     int
	Number string
	UserID 

The documentation for Importing NDF format data does not mention that the method will not be supported in future as per the message in the 'prisma import' command...

"Warning: The prisma import command will not be further developed in the future. Please use the native import features of your database for these workflows. "

https://www.prisma.io/docs/prisma-cli-and-configuration/data-import

Asynchronously returns the only element of a sequence, and throws an InvalidOperationException exception if there is not exactly one element in the sequence.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: d3b7deb0-a592-b6dc-1564-fba73a4dcb4c
• Version Independent ID: 1836b7d9-419e-d8a4-51ff-09f504a56462
• Content: [E

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

 $this->only = $this->append = $this->remove = [];

        if (empty($scene)) {
            return;
        }

现在不能使用remove方法了吗？
$validate->remove('email')->check($data);
更新到v5.1.39 LTS 后 发现这个版本把
$this->only = $this->append = $this->remove = [];
这句上移了 导致remove的被置空了

Is the README the only documentation available for this project? I find myself having to read the source to understand the interface and features that are available (e.g., context managers, bulk_query, etc.).

In the case of bulk_query, the arguments are simply passed through to the underlying SQLAlchemy engine, with no explanation. I tracked it down in [SQLAlchemy's documentation](https:/

for example，i want the Name field search with name like 、> 、<、 is null、 ... ,not only name = ?

type Dapp struct {
	UUID          string `xorm:"varchar(36) 'uuid'"`
	Name          string
	Subtitle      string
	Category      string
	Permission    string
	Synopsis      string
	Score         float64
	Logo          string
	Banner        string
	Snapshot      string
	Video     

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')
    

Setup

Versions

• Diesel: 1.4.3

Problem Description

Documentation states

fn eq_any<T>(self, values: T) -> In<Self, T::InExpression> 

Queries using this method will not be placed in the prepared statement cache

But [comments](https://github.com/diesel

Use static analyzer
Variants:
https://github.com/phpstan/phpstan
https://github.com/vimeo/psalm

Starting with jOOQ 3.12, we now generate JSON or JSONB types in generated code. If someone wanted to apply a custom binding, they should no longer use Binding<Object, Something>, but now need to use Binding<JSON[B], Something>. E.g.:

• https://www.jooq.org/doc/3.12/manual-single-page/#custom-bindings
• https://www.jooq.org/doc/3.12/manual-single-page/#custom-data-type-bindings

Here's the use case:

1. Try to connect to DB X
2. First check if it exists
   2.1 If it exists, go ahead and connect to it
   2.2 If it does not exists, create it and then connect to it

This would be essential in building a resilient system which would allow spinning up new environments quickly with no manual processes involved. I'm picturing spinning up dev/staging/prod environments with auto-

similar to how https://docs.rs/ndarray/0.12.1/ndarray/doc/index.html has a documentation module, I think this is a nice place to keep the docs in a more properly version-controlled place.

We have a abstract class in our codebase that is expanded by many documents. There is a post_save procedure we want to add to every single one of the documents that expands the base class.
Is there a way to do it?

Do I need to add signals.post_save.connectevery doc we have which will decrease maintainability on our side, I don't want to break the whole system I'm working on.

From the documentation:

Sometimes you want to be able to access an association from the opposite model. In the case of the example above, from the Person. You can do this by passing an option to the association.

Animal.hasOne('owner', Person, { reverse: "pets" });
After this, every person has now 2 convenience methods:

getPets(callback) - get all animals associated with the p

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

It would be helpful to pull comments from tables and column, and if they are present, write them as comments in the generated go code. This will help with documentation and follow the design goal: the schema is the source of truth.

If this is interesting, I can help with the mysql implementation.

反馈
IConditionalModel 不能实现多层 or条件 或者尚无此类示例
例如 select * from table where field1 = '1' and ( field2 = '2' or field3 = '3' or ( field4 = '4' and field5 = '5'))

1. What version of Go and system type/arch are you using?

go1.13.7 windows/amd64

2. What version of GoFrame are you using?

gf v1.11.4

3. Can this issue be reproduced with the latest release?

Yes

4. What did you do?

config.toml

[server]
	Address         = ":8080"

With PostgreSQL, a table consisting of a single column that is the primary key is not getting the PrimaryKey attribute set in templates/postgres.type.go.tpl. The _exists and _deleted variables are not created and update and upsert methods can not be created.

// SubnetName represents a row from 'public.subnetname'.
type SubnetName struct {
	SubnetName string `json:"subnet_name"` // subn