编写一个 bat 或 cmd 文件,内容如下:@echo offECHO 重置 Studio 3T 的使用日期......FOR /f "tokens=1,2,* " %%i IN ('reg query "HKEY_CURRENT_USER\Software\JavaSoft\Prefs\3t\mongochef\enterprise" ^| find /V "installation" ^| find /V "HKEY"') DO ECHO yes | reg add "HKEY_CURRENT_USER\Software\JavaSoft\Prefs\3t\mongochef\enterprise" /v %%i /t REG_SZ /d ""ECHO 重置完成, 按任意键退出......pause>nulexit 运行即可破解试用, 另外可以加到开机启动运行
下列是我从网上搜集并做的一个整理,若有未提及地方请指出:从 sqlite 数据库导入到 mysql 数据库实例 从 sqllite 中导出数据文件库 XX.sql 的文件。导入到 mysql 数据库中。键入命令: source /smb/works/mysql.sql出现很多如下的错误:You have an error in your SQL syntax; check the manual thatcorresponds to your MariaDB server version for the right syntax to use near XXXXXXXXX原因是 sqllite 与 mysql 语句有很大的区别:左边为 MYSQL、右边为 SQLite1、启动事务 Mysql 为 start transactionSqlite 为 begin transaction2、提交事务Mysql 为 commitSqlite 为 commit transaction 因此需要移除所有的 [BEGIN TRANSACTION] [COMMIT] 以及 任何包含 [sqlite_sequence] 的 (整) 行3 创建表 Mysql 的库名、表名、列明等都不需要使用[]sqlite 所有的名称都需要增加[]4、数据类型sqlite 的数据类型 mysql 都支持。但是 sqlite 中定义了范围在 mysql 中导入会报错。只有 varchar 需要定义范围。5、冲突解决SQLite 的 ONCONFLICT 子句不是独立的 SQL 命令。这是一条可以出现在许多其他 SQL 命令中的非标准的子句。在 Mysql 中不支持。6、引号 将 ["] 改为 [`]也可以移除全部的 ["] ,但是如果有一些函数名作为字段名 (e.g. regexp) 时将会遇到错误 需要注意一些默认为 ["] ,其作用不在字段上的,不应被替换而应当被保留 7、将所有 [autoincrement] 改为 [auto_increment]8、将所有 ['f'] 改为 ['0'] 并将所有 ['t'] 改为 ['1'] 或者 ['False'] 改为 ['0'] 及['True']改为 ['1']9、text 字段不能设置 unipue,需改为 varchar(255)10、注意 sqlite 是不区分类型的,所以有些整形字段和 text 字段要修改配合 mysql。11、默认设为 CURRENT_TIMESTAMP 的字段类型一定为 TIMESTAMP。另外还有其他可能不同的字段类型在导入 sql 报错时候可以百度解决 将修改完的 sql 文件保存,然后通过工具导入到 mysql 中即可。参考原文:https://www.2cto.com/database/201604/501991.html https://blog.csdn.net/duomoke/article/details/48246229当然最后来个最简单 sqlite 转 MySQL 方法,可以使用 sqliteToMysql 软件一键转换,只需要选择原 db 地址及目标 MySQL 地址即可,下载链接如下(有内购 不过可以免费试用):链接:https://pan.baidu.com/s/18mEN4JfHffseYf9N3GCeyA 提取码:9vv9
在 Oracle 中选择具体时间区间只需将字符用 to_date 进行转换成时间即可。但是在 postgresql 中是不是发现没效果咯?! 测试发现 pgsql 中的 to_date 真的是将时间转换成日期,而非精确到分秒,如下 sql:select * from LOG a where a.CREATE_TIME >= to_date('2019-01-08 00:00:00','yyyy-MM-dd HH24:mi:ss') and a.CREATE_TIME <= to_date('2019-01-08 16:30:43','yyyy-MM-dd HH24:mi:ss')这样写虽然具体时间不一样,但是由于转换的是日期因此两实际时间在 pgsql 中是一样的,这种情况只需 要将 to_date 改成 to_timestamp 即可,以后注意 pgsql 中 to_date 返回的是日期,非具体时间。
当执行以下命令安装依赖时候:yum -y install libaio.so.1 libgcc_s.so.1 libstdc++.so.6 时候出现了如下错误:Loaded plugins: fastestmirror, refresh-packagekit, securityLoading mirror speeds from cached hostfile * base: centos.ustc.edu.cn * extras: centos.ustc.edu.cn * updates: mirrors.cn99.comSetting up Install ProcessResolving Dependencies--> Running transaction check---> Package libaio.i686 0:0.3.107-10.el6 will be installed---> Package libgcc.i686 0:4.4.7-23.el6 will be installed---> Package libstdc++.i686 0:4.4.7-23.el6 will be installed--> Finished Dependency ResolutionError: Multilib version problems found. This often means that the root cause is something else and multilib version checking is just pointing out that there is a problem. Eg.: 1. You have an upgrade for libgcc which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of libgcc of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude libgcc.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of libgcc installed, but yum can only see an upgrade for one of those arcitectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of libgcc installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: libgcc-4.4.7-23.el6.i686 != libgcc-4.4.7-4.el6.x86_64 You could try using --skip-broken to work around the problem** Found 6 pre-existing rpmdb problem(s), 'yum check' output follows:1:libreoffice-core-4.0.4.2-9.el6.x86_64 has missing requires of libjawt.so()(64bit)1:libreoffice-core-4.0.4.2-9.el6.x86_64 has missing requires of libjawt.so(SUNWprivate_1.1)(64bit)1:libreoffice-ure-4.0.4.2-9.el6.x86_64 has missing requires of jre >= ('0', '1.5.0', None)2:postfix-2.6.6-2.2.el6_1.x86_64 has missing requires of libmysqlclient.so.16()(64bit)2:postfix-2.6.6-2.2.el6_1.x86_64 has missing requires of libmysqlclient.so.16(libmysqlclient_16)(64bit)2:postfix-2.6.6-2.2.el6_1.x86_64 has missing requires of mysql-libs 解决方法也很简单,用下列代码执行安装即可:yum install --setopt=protected_multilib=false libaio.so.1 libgcc_s.so.1 libstdc++.so.6
1.timestamp 类型 create table manager(id int not null primary key,mdate timestamp not null default current_timestamp);2.datetime 类型 create table manager(id int not null primary key,mdate datetime);