一个CREATE TABLE的小问题 ERROR: could not form array type name for type

已于 2023-04-05 17:07:36 修改
阅读量1.6k 收藏
点赞数 1
文章标签： 数据库 sql postgresql
于 2023-04-05 17:05:14 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/u010825173/article/details/129973298
版权

ERROR: could not form array type name for type
遇到了一个用户创建表的报错。比较有意思。一起来看看这个问题。

众所周知，PG的relname最大只有63，如果超过63则会自动截断。
类似这样

xxx=# create table xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60xxxx(c1 int,c2 varchar,c3 varchar,c4 varchar);
NOTICE:  identifier "xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60xxxx" will be truncated to "xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60xxx"
CREATE TABLE

当我需要批量创建99张表，并通过数字后缀来区分，如果用户的表名刚好用满63个字符时，那么就会在创建尾数71号表的时候出现这个报错，
ERROR: could not form array type name for type “xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_71”

这个报错是创建类型时的报错。postgres每创建一张表，会默认创建出一个和表相同的组合类型和数组类型。这里似乎有什么瓶颈。

先尝试复现一下。

xxx=# CREATE OR REPLACE  procedure create_tables(schema_name text, table_prefix text, num_tables integer) AS $$
DECLARE
  i integer;
  table_name text;
  sql_query text;
BEGIN
  drop schema if exists xxx cascade;
  create schema if not exists xxx; 
  FOR i IN 1..num_tables LOOP
    table_name := table_prefix || '_' || i;
    sql_query := 'CREATE TABLE ' || schema_name || '.' || table_name || ' (id int PRIMARY KEY, name TEXT)';
    execute sql_query;
    commit;
  END LOOP;
END;
$$ LANGUAGE plpgsql;
CREATE PROCEDURE
xxx=# call create_tables('xxx', 'xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60', 99);
NOTICE:  schema "xxx" does not exist, skipping
ERROR:  could not form array type name for type "xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_71"
CONTEXT:  SQL statement "CREATE TABLE xxx.xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_71 (id int PRIMARY KEY, name TEXT)"
PL/pgSQL function create_tables(text,text,integer) line 12 at EXECUTE

可以看到，这种场景下，我们创建表到70个之后就无法继续创建默认类型了。
是什么原因导致的呢？我们看下报错出处。

可以看到数据库在创建默认类型的规则，对于冲突的处理是在函数makeUniqueTypeName中进行的。

而makeUniqueTypeName函数中对于冲突的名字是通过在typname前面加下划线的方式来处理的，如果还是冲突，那就继续在前面再加一个下划线，这种方式略显粗暴。

当typname超过63，则会使用truncate_identifier函数截断。typname被截断之后，最后的几个特异性字符就会丢失，导致类型名重复，然后会一直尝试加下划线，随着下划线的增加，最终下划线会将63字节全部占满，导致无法创建。
看下typname

xxx=# select typname from pg_type where typowner !=10;
                             typname                             
-----------------------------------------------------------------
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_1
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_1
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_2
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_2
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_3
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_3
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_4
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_4
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_5
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_5
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_6
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_6
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_7
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_7
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_8
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_8
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_9
 _xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_9
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_10
 __xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_11
 ___xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_12
 ____xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx6
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_13
 _____xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_14
 ______xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_15
 _______xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_16
 ________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_17
 _________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_18
 __________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_19
 ___________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_20
 ____________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50x
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_21
 _____________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_22
 ______________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx5
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_23
 _______________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_24
 ________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_25
 _________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_26
 __________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_27
 ___________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_28
 ____________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_29
 _____________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_30
 ______________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40x
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_31
 _______________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_32
 ________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx4
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_33
 _________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_34
 __________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_35
 ___________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_36
 ____________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_37
 _____________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_38
 ______________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_39
 _______________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30xx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_40
 ________________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30x
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_41
 _________________________________xxxxxxxx10xxxxxxxx20xxxxxxxx30
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_42
 __________________________________xxxxxxxx10xxxxxxxx20xxxxxxxx3
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_43
 ___________________________________xxxxxxxx10xxxxxxxx20xxxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_44
 ____________________________________xxxxxxxx10xxxxxxxx20xxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_45
 _____________________________________xxxxxxxx10xxxxxxxx20xxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_46
 ______________________________________xxxxxxxx10xxxxxxxx20xxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_47
 _______________________________________xxxxxxxx10xxxxxxxx20xxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_48
 ________________________________________xxxxxxxx10xxxxxxxx20xxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_49
 _________________________________________xxxxxxxx10xxxxxxxx20xx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_50
 __________________________________________xxxxxxxx10xxxxxxxx20x
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_51
 ___________________________________________xxxxxxxx10xxxxxxxx20
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_52
 ____________________________________________xxxxxxxx10xxxxxxxx2
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_53
 _____________________________________________xxxxxxxx10xxxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_54
 ______________________________________________xxxxxxxx10xxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_55
 _______________________________________________xxxxxxxx10xxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_56
 ________________________________________________xxxxxxxx10xxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_57
 _________________________________________________xxxxxxxx10xxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_58
 __________________________________________________xxxxxxxx10xxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_59
 ___________________________________________________xxxxxxxx10xx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_60
 ____________________________________________________xxxxxxxx10x
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_61
 _____________________________________________________xxxxxxxx10
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_62
 ______________________________________________________xxxxxxxx1
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_63
 _______________________________________________________xxxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_64
 ________________________________________________________xxxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_65
 _________________________________________________________xxxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_66
 __________________________________________________________xxxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_67
 ___________________________________________________________xxxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_68
 ____________________________________________________________xxx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_69
 _____________________________________________________________xx
 xxxxxxxx10xxxxxxxx20xxxxxxxx30xxxxxxxx40xxxxxxxx50xxxxxxxx60_70
 ______________________________________________________________x
(140 rows)

当第10个表创建的时候，因其名称被截断，所以开始加下划线，一直加到63个字符，最终只能创建61+9张表。所以会报错在第70张表上。

这种问题如何解决呢？
之前的想法是在命名规则里面增加一个特异性数字。
不过刚才看到社区搜到修复的patch已经合入master了。不用我们操心了，直接看下patch，思路是截断的时候多截断一些字符，然后把一个数字拼接进去。
https://github.com/postgres/postgres/commit/70988b7b0a0bd03c59a2314d0b5bcf2135692349

	/*
	 * Per ancient Postgres tradition, array type names are made by prepending
	 * an underscore to the base type name.  Much client code knows that
	 * convention, so don't muck with it.  However, the tradition is less
	 * clear about what to do in the corner cases where the resulting name is
	 * too long or conflicts with an existing name.  Our current rules are (1)
	 * truncate the base name on the right as needed, and (2) if there is a
	 * conflict, append another underscore and some digits chosen to make it
	 * unique.  This is similar to what ChooseRelationName() does.
	 *
	 * The actual name generation can be farmed out to makeObjectName() by
	 * giving it an empty first name component.
	 */

	/* First, try with no numeric suffix */
	arr_name = makeObjectName("", typeName, NULL);

	for (;;)
	{
		if (!SearchSysCacheExists2(TYPENAMENSP,
								   CStringGetDatum(arr_name),
								   ObjectIdGetDatum(typeNamespace)))
			break;

		/* That attempt conflicted.  Prepare a new name with some digits. */
		pfree(arr_name);
		snprintf(suffix, sizeof(suffix), "%d", ++pass);
		arr_name = makeObjectName("", typeName, suffix);
	}
泰勒你好
关注
  • 1
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
create table时报错
zhaolixin0726的博客
07-24 2997
今天在linux服务器的数据库中创建了一个表，语法如下： create table apidoc {`id` int(11) NOT NULL ,  `nodeId` varchar(12) NOT NULL,  `parentId` varchar(12) NOT NULL ,  `hrefAddress` varchar(85) ,  `nodeName` varchar(20)
8-07-14_MegaCLI for linux_windows
03-15
SCGCQ00318648 Defect VD creation on regular drives fails for older firmware where 4K sector is not supported SCGCQ00319423 Defect FreeBSD MegaCLI v8.05.02 does not detect controller when driver 5.504....
ERROR: could not find array type for data type information_schema.character_data
乡下人
04-28 617
SELECT table_schema, TABLE_NAME, array_to_json ( ARRAY_AGG ( privilege_type ) ) AS privilege_type FROM information_schema.table_privileges t3 WHERE t3.grantee = 'user1' GROUP BY table_schema, TABLE_NAME 报错：> ERROR: could not find a..
Mysql create table 建表报错: Row size too large. The maximum row size for the used table type, not count
日常记录
12-12 1750
原因： mysql单表所有行定义大小之和不得超过65535，除TEXT/BLOB类型 UTF-8:一个汉字占3个字节,字母1个字节。 GBK:一个汉字占2个字节,字母2个字节。 解决方案： 将长文本类型属性改为TEXT或者在合理要求内降低varchar的最大范围等，总之要符合以上规则 可以将长文本分表存储提高查询效率
Mysql create table Error:1005
chanllen的专栏
11-04 350
I realize this is an old post, but it ranks high in Google, so I'm adding what I figured out for MY problem. If you have a mix of table types (e.g. MyISAM and InnoDB), you will get this error as wel
mysql sqlcode_mysql – SQL CREATE TABLE错误
weixin_42515377的博客
01-27 334
答案是我使用了错误的引号而不是反引号.愚蠢的语法hilighter欺骗了我.在过去的半小时里,我一直坚持这个简单的事情,所以我想我可以尝试在这里快速回答一下.假设我使用的是mysql 5.1,那么我的SQL语法究竟是什么不正确CREATE TABLE 'users' ('id' INT(11) UNSIGNED NOT NULL AUTO_INCREMENT PRIMARY KEY,'userna...
occam一维反演
04-21
C AS THE ARRAY SIZES FOR THE 2D PROBLEM ARE NOW GETTING TOO LARGE FOR COMFORT. C INCLUDE FILES ARE NOW USED TO STREAMLINE CHANGES OF DIMENSION. C IMPLICIT DOUBLE PRECISION HAS BEEN REMOVED, AGAIN FOR ...
在RedHat上安装部署Apache+MySQL+PHP环境.docx
08-08
Name: <input type='text' name='uid' /> text: <input type='text' name='text' /> <input type='submit'></form>"; mysql_close($conn); ?> ``` **3. 插入数据** 创建一个名为`insert.php`的文件，用于向数据库...
PHP+MYSQL留言板制作教程
07-31
CREATE TABLE IF NOT EXISTS `content` ( `id` int(11) NOT NULL auto_increment, `name` varchar(20) NOT NULL, `email` varchar(50) NOT NULL, `content` varchar(200) NOT NULL, PRIMARY KEY (`id`) ) ...
php经典例子
02-25
CREATE TABLE IF NOT EXISTS `content` ( `id` int(11) NOT NULL auto_increment, `name` varchar(20) NOT NULL, `email` varchar(50) NOT NULL, `content` varchar(200) NOT NULL, PRIMARY KEY (`id`) ) ...
mysql 1005 - can't create table_关于创建数据表报错一例(ERROR 1005 Can’t create table (errno: 121))...
weixin_42594419的博客
01-21 1244
问题描述曾遇到创建数据表报错问题，报错如下：ERROR 1005 (HY000) at line 18: Can't create table 'db1.t2' (errno: 121)通过日志查看有一条记录InnoDB: Error: table `db1`.`t2` already exists in InnoDB internal可见要创建的这个表已经存在，导致创建同名数据表报错，但是从数据...
记一次hive建表报错
激进的蜗牛
11-22 1991
执行create table table_name xxx as select xxx的语句 语句如下 create table table1 STORED as ORC TBLPROPERTIES ('orc.compress'='SNAPPY') as select field1 as `名字1`, field2 as `名字2`, from table2 报错如下 Query I...
MyBatis动态创建表报错解决
smileLs的博客
05-28 1170
转载 dao int insert(@Param("tableName")String tableName,@Param("trackpoint")Trackpoint trackpoint); mapper <insert id="insert" parameterType="xx.xxx.xx.po.Trackpoint"> insert into ${ta...
XXXXXXXXXXX
热门推荐
roroyangivan的专栏
10-31 7万+
package thread; public class VolatileTest { public static volatile int race = 0; public static void increase(){ race++; } private static final int THREAD_COUNT = 20; public
HEAP: Free Heap block xxxxxxxx modified at xxxxxxxx after it was freed
~ 飞 扬 的 天 空 ~
01-14 5万+
http://blog.sina.com.cn/s/blog_a17b071c01015rwd.html 《诸子百家》发布后，发现游戏在有些情况下会崩溃。偶然崩溃。        由于我是负责主框架，网络协议和登录，数据等，所以这个修正bug的任务主要就落在我头上了。               一、bug        1.最头疼的bug     
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
u014483623的专栏
04-02 2万+
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
spoj XXXXXXXX
anantheparty的博客
03-17 1万+
树套树裸题，留个版 （树状数组套平衡树）#include<bits/stdc++.h> #define ll long long #define INF 1000000000 #define mp make_pair #define clr(x) memset(x,0,sizeof(x))using namespace std;inline int read() { register in
mybatis动态创建表
恨_别离的博客
10-11 4634
mybatis
PostgreSQL 创建分区表
zhangyupeng0528的博客
08-05 1万+
PG 假如我们想像Hive那也创建动态分区是不能实现的。 那么需要我们手动通过脚本来创建分区表，创建分区表必须要创建主表和分区表。 主表：定义我们的一些约束，以及分区键，实质上不存储数据 分区表：主要是用来存储数据的。所有列及约束都跟随主表 注意：如果我们指定分区表不存在会报错，因此一定要提前创建好分区表，并且要数据不能有遗漏的分区键。 列分区表 就是我们指定数据库中字段的一列作为分区字段。 1.如下创建分区表的主表 关键字【partition by list...
error: could not create the java virtual machine. error: a fatal exception h
最新发布
09-16
"error: could not create the Java virtual machine. error: a fatal exception h" 是一个Java虚拟机创建失败的错误信息。 出现这个错误通常是由于以下几个原因： 1. 内存不足：Java虚拟机需要一定的内存空间来执行程序，如果可用内存不足，就会出现该错误。解决方法是增加可用内存，可以通过编辑Java配置文件来调整虚拟机的内存分配。 2. 系统限制：如果操作系统对程序运行有限制，如最大堆大小限制或最大线程数量限制等，也会导致Java虚拟机创建失败。解决方法是增加操作系统对Java程序的限制。 3. Java版本不匹配：某些情况下，一些Java应用程序会要求特定版本的Java虚拟机才能正确运行，如果安装的Java版本不匹配，就会出现该错误。解决方法是检查需要的Java版本，并正确安装对应的版本。 4. 环境变量设置错误：Java虚拟机需要正确设置的环境变量来定位Java安装路径等信息，如果设置错误，就会导致虚拟机创建失败。解决方法是检查环境变量设置，并进行修正。 总之，"error: could not create the Java virtual machine. error: a fatal exception h"错误可能由多种原因引起，具体解决方法需要根据实际情况来确定。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值