如何格式化 ISQL Perform 中 DATETIME 列的显示？..以及其他 4.10 相关问题
Informix-SE 4.10.DD6、Informix-SQL 4.10.DC1 执行屏幕：
1) 我将列定义为 DATETIME HOUR TO MINUTE，当我在 ISQL Perform 屏幕中显示它时，其默认格式为 HH:MM（24 小时时间）。我想将其显示为 HH:MM（上午/下午）。执行格式属性仅适用于 DATE 和 DECIMAL 数据类型。如何设置 DATETIME 的显示格式？
2) 我可以在4.10中定义VARCHAR、TEXT和BYTE数据类型吗？我注意到 Perform 中有一个用于查看 BLOBS 的“View”命令，Perform 如何知道要显示哪个 BLOB？
3）当我将 SE 2.10.06E 文件移植到 SE 4.10.DD6 时，我注意到“pcuser”。在每个表名上都有前缀，并且我的一些 SQL 过程无法工作，并且 SYSCONST 已损坏，因此我尝试 BCHECK，但 BCHECK 无法工作。这些前缀是表所有者吗？..所以我在 2.10 中 dbschema'ed 并卸载了所有表，在 4.10 中重新创建了数据库和表，加载了所有表并且能够毫无问题地访问它们，但是 BCHECK 和 SQL 过程还是不行。
4) 任何人都可以与我分享 ISQL 4.10 手册吗？...如果您没有 4.10 (DOS) 手册，即使是 4.10U (UNIX) 手册也会有很大帮助！
Informix-SE 4.10.DD6, Informix-SQL 4.10.DC1 Perform screen:
1) I have column defined as DATETIME HOUR TO MINUTE and when I display it in ISQL Perform screen its default format is HH:MM (24-hour time). I would like to display it as HH:MM (am/pm). Perform format attribute only applies to DATE and DECIMAL datatypes. How can I format display for DATETIME?
2) Can I define VARCHAR, TEXT and BYTE datatypes in 4.10? I noticed a "View" command in Perform for viewing BLOBS, how does Perform know which BLOB to display?
3) When I ported my SE 2.10.06E files to SE 4.10.DD6 I noticed that "pcuser". was prefixed on each tablename and some of my SQL procs wouldn't work and SYSCONST got corrupted so I attempted a BCHECK and BCHECK wouldn't work. Are theses prefixes the table-owner?.. So I dbschema'ed and unloaded all my tables in 2.10, re-created database and tables in 4.10, loaded all tables and was able to access them with no problem, however BCHECK and SQL procs still dont work.
4) Anyone might have ISQL 4.10 manuals they could share with me?.. Even the 4.10U (UNIX)manuals would be a big help if you dont have the 4.10 (DOS) manuals!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
在 ISQL 7.x 中，您有机会设法以 12 小时制显示时间，但基本上，ISQL 并不真正支持它，并且在 ISQL 4.10 中，您没有内置选项根本不。但是，如果您想发挥创意，可以考虑在 DISPLAYONLY 字段中显示数据（实际数据在主屏幕外的字段中），然后使用控制时间显示的指令。当然，对其进行格式化并非易事（但绝非不可能） - 上午 12:30 早于凌晨 1:30 等 - 并且反向转换需要小心。
Informix SE 不支持 BYTE、TEXT 或 VARCHAR - 句点。 （与挑剔者无关的细节 -
SELECT "" FROM SomeWhere返回 VARCHAR(1)。）是的，“pcuser”是所有者前缀。天哪 - MODE ANSI 数据库及其所有者是在 4.00 中引入的吗？我以为那是早些时候，但我可能是错的。不管怎样，我确实记得 DB-Schema 输出开始在各处添加用户名 - 我仍然有一个 shell 脚本，它可以动态编写几个 ACE 报告，以生成无所有者模式。这可以追溯到这个时代（80 年代末）。 BCHECK 应该适用于数据库中的任何 C-ISAM 文件 - 如果不能，那么您的文件很可能已严重损坏，以致 BCHECK 无法识别它们的头部或尾部，但这种情况相对不常见。在当时，它可能不那么可靠 - 但我对 BCHECK 的经验一直是，如果信息是可挽救的，它就挽救了数据。
可能不是。我刚刚记得我有一些 90 年代中期的文档 CD（目前带有“法律”；他们需要一些旧文档来处理某些诉讼 - 我必须要求归还 CD）。 4.x 可能只是运气好而已；我 99% 确信他们没有任何早期的手册（2.x；从来没有基于 SQL 的产品的 3.x 版本 - 直到 CSDK 3.x 发布为止；无论如何，因此挂起了另一个故事，下次）。
In ISQL 7.x, you'd have an outside chance of managing to display a time in the 12-hour clock, but basically, ISQL does not really support it and in ISQL 4.10, you have no built-in options at all. However, if you want to get creative, you can consider showing the data in a DISPLAYONLY field (with the actual data in an off-the-main-screen field) and then have an instruction that controls the display of the time. Formatting that up is non-trivial (but far from impossible), of course - 12:30 am is before 1:30 am, etc - and the reverse conversion will require care.
Informix SE does not support BYTE, TEXT or VARCHAR - period. (Irrelevant detail for the nit-pickers -
SELECT "" FROM SomeWherereturns a VARCHAR(1).)Yes, 'pcuser' is the owner prefix. Gosh - were MODE ANSI databases with owners introduced in 4.00? I thought that was earlier, but I could be wrong. Anyway, I do remember that the DB-Schema output started adding user names everywhere - I still have a shell script that writes a couple of ACE reports on the fly for generating an owner-less schema. That dates back to this era (late 80s). BCHECK should work on any C-ISAM files in a database - if it doesn't, then you most probably have files which are sufficiently corrupted that BCHECK cannot make head or tail of them, but that's relatively unusual. It might not have been as reliable in those days - but my experience with BCHECK has always been that if the information was salvageable, it salvaged the data.
Probably not. I've just remembered I have some mid-90s doc CDs (currently with 'Legal'; they needed some old documentation for some litigation - I must ask for the CDs back). You might just be in some luck for 4.x; I'm 99% sure they don't have any earlier manuals (2.x; there never was a 3.x version of the SQL-based products - until CSDK 3.x was released, anyway; and thereby hangs another story, for another time).