【问题标题】:How to reduce code duplication caused by substring and instring?如何减少子字符串和字符串引起的代码重复?
【发布时间】:2014-05-06 17:22:56
【问题描述】:

我需要将一个以“\n”分隔的文本字段(描述)解析为三个单独的字段。我通过使用substrinstr 来做到这一点,但这会导致难以阅读和重复的sql。有没有办法创建和使用变量或表达式来保存 instring 函数返回的“位置”值,以便我可以将该变量传递给substr?我的代码发布在函数下方并返回正确的结果,但感觉不对。有很多重复。

相关原始数据:

DBKEY       DBTIME                      DBUSER     DESCRIPTION
40846809    2013-11-18 11:04:11.0000000 abc$userid  The following Message List entry has been logged:\nError Number:5011\nDescription:Planogram: 60E90001006.0SMA :: UPC:  is not numeric\nSeverity:0
40846810    2013-11-18 11:04:11.0000000 abc$userid  The following Message List entry has been logged:\nError Number:5000\nDescription:Planogram: 60E90001006.0SMA :: ID: NEW  not 9 digits\nSeverity:0
40846811    2013-11-18 11:04:11.0000000 abc$userid  The following Message List entry has been logged:\nError Number:5001\nDescription:Planogram: 60E90001006.0SMA :: ID: NEW  not numeric\nSeverity:0

期望的结果:

DBKEY       DBTIME                      USERID  ERROR_NUM   DESCRIPTION SEVERITY
40846809    2013-11-18 11:04:11.0000000 userid  5011        Planogram: 60E90001006.0SMA :: UPC:  is not numeric 0
40846810    2013-11-18 11:04:11.0000000 userid  5000        Planogram: 60E90001006.0SMA :: ID: NEW  not 9 digits    0
40846811    2013-11-18 11:04:11.0000000 userid  5001        Planogram: 60E90001006.0SMA :: ID: NEW  not numeric 0
40846812    2013-11-18 11:04:11.0000000 userid  5003        Planogram: 60E90001006.0SMA :: ID: NEW  ID must begin with 000,200,220,900,950,990,or 999   0

当前代码:

SELECT DBKEY,DBTIME,
        SUBSTR(DBUSER,INSTR(DBUSER,'$',1,1)+1) AS USERID,
        SUBSTR(ERROR_NUM,INSTR(ERROR_NUM,':')+1) AS ERROR_NUM,
        SUBSTR(DESC1,INSTR(DESC1,':')+1) AS DESCRIPTION,
        SUBSTR(SEVERITY,INSTR(SEVERITY,':')+1) AS SEVERITY
FROM(
    SELECT l.DBKEY,DBTIME,DBUSER,
        --substring(description,first+2,second-first-2)
        SUBSTR(DESCRIPTION,INSTR(DESCRIPTION,'\n',1,1)+2,INSTR(DESCRIPTION,'\n',1,2)-INSTR(DESCRIPTION,'\n',1,1)-2) AS ERROR_NUM,
        --substring(description,second+2,third-second-2)
        SUBSTR(DESCRIPTION,INSTR(DESCRIPTION,'\n',1,2)+2,INSTR(DESCRIPTION,'\n',1,3)-INSTR(DESCRIPTION,'\n',1,2)-2) AS DESC1,
        --substring(description,third+2) 
        SUBSTR(DESCRIPTION,INSTR(DESCRIPTION,'\n',1,3)+2) AS SEVERITY
        /*,
        INSTR(DESCRIPTION,''\n'',1,1) as first,
        INSTR(DESCRIPTION,''\n'',1,2) as second,
        INSTR(DESCRIPTION,''\n'',1,3) as third,
        */
    FROM EVENT_LOG l
)derivedtbl

【问题讨论】:

  • 一些 RDBMS 有一个原生的 SPLIT() 函数。您使用的是哪个 RDBMS?

标签: sql oracle plsql oracle11g substr


【解决方案1】:

我建议使用REGEXP_SUBSTR,这是一个很好的功能,可以达到您的预期效果:

SELECT
    l.DBKEY,
    l.DBTIME,
    REGEXP_SUBSTR(l.DBUSER, '[^$]+$')                 AS USERID,
    REGEXP_SUBSTR(l.DESCRIPTION, '[0-9]{4}')          AS ERROR_NUM,
    REPLACE(REGEXP_SUBSTR(l.DESCRIPTION, 'Planogram:[^\]+\\n'), '\n', '')
                                                      AS DESCRIPTION,
    REGEXP_SUBSTR(l.DESCRIPTION, '\d+$')              AS SEVERITY
FROM
    EVENT_LOG l;

我创建并测试了SQLFiddle。有关REGEXP_SUBSTR 的更多信息,您可能需要阅读Oracle Docs

【讨论】:

  • 您通过指向 oracle 文档的链接将他排除在外。谢谢@timo.rieber。这正是我所需要的。
  • 承认,但请注意,此方法假定错误代码始终为四位数字,并且所有描述都以“货架图:”开头。
  • 谢谢@Joe。妥当注明。我会考虑到这一点。在现实中,它当然可能是 3、4 或 5 位数。
  • 对于 3 到 5 位数字只需写 {3,5},更多正则表达式的详细信息可以在这里找到:docs.oracle.com/cd/B19306_01/server.102/b14200/…
  • @timo.rieber 是的,但您仍然面临获取错误值的风险。如果您指定 {3,5} 并显示两位数的错误代码,您最终可能会拉取描述中的前两位数。
【解决方案2】:

regexp_replace 会做到的:

select 
  dbkey,
  dbtime,
  REGEXP_REPLACE(dbuser,'^.*\$','',1,1) dbuser,
  REGEXP_REPLACE(description, '.*Error Number:([0-9]+).*','\1',1,1) error_num,
  REGEXP_REPLACE(description, '.*Description:(.+)\\n.*','\1',1,1) description,
  REGEXP_REPLACE(description, '.*Severity:(.+)','\1',1,1) severity
from rawdata;

结果

DBKEY       DBTIME                      DBUSER  ERROR_NUM  DESCRIPTION                                         SEVERITY
40846809    2013-11-18 11:04:11.0000000 userid  5011       Planogram: 60E90001006.0SMA :: UPC: is not numeric       0
40846810    2013-11-18 11:04:11.0000000 userid  5000       Planogram: 60E90001006.0SMA :: ID: NEW not 9 digits      0
40846811    2013-11-18 11:04:11.0000000 userid  5001       Planogram: 60E90001006.0SMA :: ID: NEW not numeric       0

SQLFiddle here

【讨论】:

    猜你喜欢
    • 2017-02-14
    • 2019-06-03
    • 2015-02-10
    • 2013-05-18
    • 1970-01-01
    • 2022-01-13
    • 2011-10-22
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多