blocks|key|2635918|text|我切换到typeorm版本的0.1.0-alpha.40，在创建连接时有autoSchemaSync选项，这使得它可以工作：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2635919|createConnection({
++type:+'mysql',
++host:+'typeorm2.cn32tstd6wqk.eu-central-1.rds.amazonaws.com',
++port:+1234,
++username:+'username',
++password:+'password',
++database:+'dbname',
++entities:+[
++++//+__dirname+%2B+'/../**/*.entity{.ts,.js}'
++++UserPassword,
++++User
++],
++autoSchemaSync:+true,
})|code-block|syntax|javascript|2635920|entityMap^0|E|E|10|E|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|S|8|@]|E|@]|F|$J|K]]|$1|L|3|-4|5|6|7|T|8|@]|E|@]|F|$]]]|M|$]]

I switched to typeorm version 0.1.0-alpha.40 that has the option <code>autoSchemaSync</code> when creating a connection, which made it work:

<pre><code>createConnection({
 type: 'mysql',
 host: 'typeorm2.cn32tstd6wqk.eu-central-1.rds.amazonaws.com',
 port: 1234,
 username: 'username',
 password: 'password',
 database: 'dbname',
 entities: [
 // __dirname + '/../**/*.entity{.ts,.js}'
 UserPassword,
 User
 ],
 autoSchemaSync: true,
})
</code></pre>

blocks|key|99859|text|连接具有“synchronize()”方法。您可以使用它自动创建表和列：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|99860|const+connection+=+await+createConnection(...);
await+connection.synchronize();|code-block|syntax|javascript|99861|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Connection has ‘synchronize()’ method. You can use it to create tables and columns automatically:

<pre><code>const connection = await createConnection(...);
await connection.synchronize();
</code></pre>

blocks|key|102851|text|通过将以下内容添加到ormconfig.json/js/xml/etc|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|102852|synchronize:+true++|code-block|syntax|javascript|102853|如果表不存在，它会创建一次表。|102854|entityMap^0|A|P|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|N|$]]

By adding the following to <code>ormconfig.json/js/xml/etc</code>:

<pre><code>synchronize: true 
</code></pre>

It creates the table once if it does not exists.

blocks|key|99875|text|尽管前面的答案对于开发环境是可以接受的，但是对于生产来说它们是错误的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|99876|您正在寻找的是迁移。迁移在建立连接并记录时执行-任何迁移都不会运行多次。TypeORM还提供了命令行工具，允许您生成迁移(read+more+here)，从而大大加快了创建迁移的速度。TypeORM还使用时间戳前缀标记每个迁移，以确保它们将按正确的顺序运行-有时您可能希望首先在主表中运行迁移，有时在支持表上运行迁移。在配置连接时，您可以像这样加载迁移：|99877|createConnection({
++++type:+'mysql',
++++host:+'typeorm2.cn32tstd6wqk.eu-central-1.rds.amazonaws.com',
++++port:+1234,
++++username:+'username',
++++password:+'password',
++++database:+'dbname',
++++entities:+[
++++++++//+__dirname+%2B+'/../**/*.entity{.ts,.js}'
++++++++UserPassword,
++++++++User
++++],
++++migrations:+['./migrations/*.js'],
++++synchronize:+false
})|code-block|syntax|javascript|99878|迁移由两部分组成-+up+(迁移代码)和down+(恢复迁移的代码)。简单的例子：|99879|import+{+MigrationInterface,+QueryRunner+}+from+'typeorm';

export+class+AddImageToUser+implements+MigrationInterface+{

++++async+up(queryRunner:+QueryRunner):+Promise<any>+{
++++++++await+queryRunner.query(
++++++++++++++++'ALTER+TABLE+"user"+ADD+image+varchar(255)'
++++++++);
++++}
++++async+down(queryRunner:+QueryRunner):+Promise<any>+{
++++++++await+queryRunner.query(
++++++++++++++++'ALTER+TABLE+"user"+DROP+COLUMN+image'
++++++++);
++++}
}|99880|如果你想阅读更多，TypeORM有他们官方Git仓库here的详细描述|99881|通常，将数据和模式的同步留给框架是不好的。这是您应该做的事情，以确保数据库模式将被保留。我之前链接的CLI还允许您运行迁移，从而在将更改推送到生产环境之前对其进行测试。|99882|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/typeorm/typeorm/blob/master/docs/using-cli.md#create-a-new-migration|1|https://github.com/typeorm/typeorm/blob/master/docs/migrations.md#creating-a-new-migration^0|9|2|0|1P|E|0|0|0|A|2|K|4|0|0|Q|4|1|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@$9|15|A|16|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|H|3|I|5|J|7|1B|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1H|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1I|8|@]|D|@$9|1J|A|1K|1|1L]]|E|$]]|$1|S|3|T|5|6|7|1M|8|@]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1N|8|@]|D|@]|E|$]]]|V|$W|$5|X|Y|Z|E|$10|11]]|12|$5|X|Y|Z|E|$10|13]]]]

Even though the previous answers are acceptable for development environment, they are wrong for production.
What you are looking for are migrations. Migrations are executed when connection is established and are recorded - no migration will run more than once. TypeORM also provides CLI which allows you to generate migrations (<a href="https://github.com/typeorm/typeorm/blob/master/docs/using-cli.md#create-a-new-migration" rel="noreferrer">read more here</a>), making it much faster to create them. TypeORM also marks each migration with a timestamp prefix, ensuring they will run in proper sequence - sometimes you might want to run migrations in primary tables first, sometimes on supporting tables. When configuring connection, you load migrations like this:
<pre class="lang-js prettyprint-override"><code>createConnection({
 type: 'mysql',
 host: 'typeorm2.cn32tstd6wqk.eu-central-1.rds.amazonaws.com',
 port: 1234,
 username: 'username',
 password: 'password',
 database: 'dbname',
 entities: [
 // __dirname + '/../**/*.entity{.ts,.js}'
 UserPassword,
 User
 ],
 migrations: ['./migrations/*.js'],
 synchronize: false
})
</code></pre>
Migrations are built composed of 2 parts - up (migration code) and down (code to revert migration). Simple example:
<pre class="lang-js prettyprint-override"><code>import { MigrationInterface, QueryRunner } from 'typeorm';

export class AddImageToUser implements MigrationInterface {

 async up(queryRunner: QueryRunner): Promise&lt;any&gt; {
 await queryRunner.query(
 'ALTER TABLE &quot;user&quot; ADD image varchar(255)'
 );
 }
 async down(queryRunner: QueryRunner): Promise&lt;any&gt; {
 await queryRunner.query(
 'ALTER TABLE &quot;user&quot; DROP COLUMN image'
 );
 }
}
</code></pre>
If you want to read more, TypeORM has detailed description on their official Git repository <a href="https://github.com/typeorm/typeorm/blob/master/docs/migrations.md#creating-a-new-migration" rel="noreferrer">here</a>
In general, it is not good to leave the synchronization of the data and schema to the framework. It is something that should be done by you to ensure the database schema will be preserved. The CLI I linked before also allows you to run migrations and therefore test them before pushing changes to production.

blocks|key|102880|text|对我来说，问题是我想要为其生成迁移的实体不是一个导出的类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|102881|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

For me the problem was that the Entity I wanted to generate migration for was not an exported class.

blocks|key|100511|text|帮助我的是将模型的名称添加到"Entity()“装饰器中：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|100512|@Entity({+name:+'User'+})|code-block|syntax|javascript|100513|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What helped me was adding the name of the model to the "Entity()" decorator:

<pre><code>@Entity({ name: 'User' })
</code></pre>

blocks|key|2847670|text|手动指定实体而不是通配符路径名对我有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2847671|export+let+dbOptions:+ConnectionOptions+=+{
+++++type:+"mysql",
+++++host:+"localhost",
+++++port:+3306,
+++++username:+"root",
+++++password:+"root",
+++++database:+"exam",
+++++synchronize:+true,

+++++entities:+[
++++++++++//+"./entities/*.js",+++++//+Wildcard+Path+:+Not+working
++++++++++EmployeeEntity++++++++++++//+Specify+the+entities+directly.
+++++]
}|code-block|syntax|javascript|2847672|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Manually specifying entities instead of the wildcard path name worked for me.

<pre><code>export let dbOptions: ConnectionOptions = {
 type: "mysql",
 host: "localhost",
 port: 3306,
 username: "root",
 password: "root",
 database: "exam",
 synchronize: true,

 entities: [
 // "./entities/*.js", // Wildcard Path : Not working
 EmployeeEntity // Specify the entities directly.
 ]
}
</code></pre>

blocks|key|2636166|text|在您的ormconfig.json文件中设置"synchronize"-->+true+(布尔值)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2636167|这应该是可行的|2636168|​|2636169|{
++++"type":+"mysql",
++++"host":+"localhost",
++++"port":+5432,
++++"username":+"root",
++++"password":+"root",
++++"database":+"Identity_Demo",
++++"synchronize":+true,
++++"logging":+true,
++++"entities":+["dist/**/*.entity.js"]
+}|code-block|syntax|javascript|2636170|2636171|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Q|8|@]|9|@]|A|$I|J]]|$1|K|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|M|$]]

In your ormconfig.json file set &quot;synchronize&quot;--&gt; true (boolean)
This should work
<div class="snippet" data-lang="js" data-hide="false" data-console="true" data-babel="true">
<div class="snippet-code">
<pre class="snippet-code-html lang-html prettyprint-override"><code>{
 "type": "mysql",
 "host": "localhost",
 "port": 5432,
 "username": "root",
 "password": "root",
 "database": "Identity_Demo",
 "synchronize": true,
 "logging": true,
 "entities": ["dist/**/*.entity.js"]
 }</code></pre>
</div>
</div>

blocks|key|2847724|text|类似于Jose+Miguel的回答|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2847725|如果您第一次使用typeorm-model-generator生成从DB到代码的实体，那么typeorm-model-generator可能已经生成了如下代码。|offset|length|style|CODE|2847726|@Entity('yourTableName',+{+schema:+'public'+})|code-block|syntax|javascript|2847727|我删除了{+schema:+'public'+}，让它看起来像|2847728|@Entity('yourTableName')|2847729|这为我解决了这个问题。希望它能在未来对某人有所帮助:)|2847730|entityMap^0|0|8|N|19|N|0|0|4|K|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|O|3|P|5|J|7|14|8|@]|9|@]|A|$K|L]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|16|8|@]|9|@]|A|$]]]|T|$]]

Similar to Jose Miguel's answer
If you used <code>typeorm-model-generator</code> to generate your entities for the first time from the DB to the code then maybe <code>typeorm-model-generator</code> might have generated your code with something like this.
<pre><code>@Entity('yourTableName', { schema: 'public' })
</code></pre>
I removed <code>{ schema: 'public' }</code> leaving it like
<pre><code>@Entity('yourTableName')
</code></pre>
this fixed the issue for me.
Hope it helps someone in the future :)

blocks|key|2636225|text|我也有同样的问题。只需添加|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2636226|...
synchronize:+true,
...|code-block|syntax|javascript|2636227|到TypeOrm配置|2636228|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had the same issue. Just add
<pre><code>...
synchronize: true,
...
</code></pre>
to TypeOrm configs

blocks|key|2847745|text|我有个愚蠢的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2847746|所有的配置都是正确的，只有我的实体文件在所有更改后没有保存。|2847747|一定要打开自动保存。|2847748|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I had a stupid issue.
All the configuration was correct, just my entity file was not saved after all the changes.
Should definitely turn on auto save.

I have set up a system with typeorm (<a href="https://github.com/typeorm/typeorm" rel="noreferrer">https://github.com/typeorm/typeorm</a>) and NestJs (<a href="https://github.com/nestjs/nest" rel="noreferrer">https://github.com/nestjs/nest</a>), but TypeORM isn't creating the tables or columns. My setup is like this:
<pre class="lang-js prettyprint-override"><code>import {UserPassword} from '../user/user-password.entity';
import {User} from '../user/user.entity';

createConnection({
 type: 'mysql',
 host: 'typeorm2.cn32tstd6wqk.eu-central-1.rds.amazonaws.com',
 port: 1234,
 username: 'username',
 password: 'password',
 database: 'dbname',
 entities: [
 // __dirname + '/../**/*.entity{.ts,.js}'
 UserPassword,
 User
 ]
 })
</code></pre>
And the entities are:
<pre class="lang-ts prettyprint-override"><code>import {Entity, Column, PrimaryGeneratedColumn, OneToOne, JoinColumn} from 'typeorm';

@Entity()
export class UserPassword {

 @PrimaryGeneratedColumn()
 id: number;

 @Column()
 hash: string;

 @Column()
 algorithm: string;

}
</code></pre>
and
<pre class="lang-ts prettyprint-override"><code>import {Entity, Column, PrimaryGeneratedColumn, OneToOne, JoinColumn} from 'typeorm';
import {UserPassword} from './user-password.entity';

@Entity()
export class User {
 @PrimaryGeneratedColumn()
 id: number;

 @Column({ length: 35 })
 firstName: string;

 @Column({ length: 35 })
 lastName: string;

 @Column({ length: 50})
 mail: string;

 @OneToOne(type =&gt; UserPassword)
 @JoinColumn()
 password: UserPassword;

}
</code></pre>
Then I try to create a user like this:
<pre class="lang-ts prettyprint-override"><code>// ... some code
await this.userPasswordRepository.save(userPassword);
return await this.userRepository.save(user);
</code></pre>
But I get the following error:
<blockquote>
QueryFailedError: ER_NO_SUCH_TABLE: Table 'typeorm2.user_password' doesn't exist
</blockquote>
When I insert the table manually then I get the error:
<blockquote>
QueryFailedError: ER_BAD_FIELD_ERROR: Unknown column 'hash' in 'field list'
</blockquote>
So it seems like TypeORM doesn't generate the tables / columns. Does anyone know why this could be?

TypeORM does not create tables, columns etc

命令行工具

数据库

我已经用typeorm ()和NestJs ()设置了一个系统，但是TypeORM没有创建表或列。我的设置如下：import {UserPassword} from '../user/user-password.entity';import {User} from '../user/user.entity';creat...

问TypeORM不创建表、列等
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问TypeORM不创建表、列等EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问TypeORM不创建表、列等
EN