当前位置：theitroad>在 Oracle 中表示 IPv4/IPv6 地址

在 Oracle 中表示 IPv4/IPv6 地址

声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow 原文地址: http://stackoverflow.com/questions/4950394/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me): StackOverFlow

提示：将鼠标放在中文语句上可以显示对应的英文。显示中英文
时间：2020-09-18 22:42:14 　来源:igfitidea点击:

Representing IPv4/IPv6 addresses in Oracle

oracleipv6ipv4

提问by pilcrow

In Oracle, what is the appropriate data type or technique for representing network addresses, which addresses may be IPv4 or IPv6?

在 Oracle 中，表示网络地址的适当数据类型或技术是什么，哪些地址可能是 IPv4 或 IPv6？

Background: I'm converting a table recording network activity, built using the PostgreSQL inetdata typeto hold both v4 and v6 addresses in the same table.

背景：我正在转换一个记录网络活动的表，该表使用 PostgreSQLinet数据类型构建以将 v4 和 v6 地址保存在同一个表中。

No row contains both v4 and v6 addresses, however. (That is, a record is either from a machine's v4 stack, or a machine's v6 stack.)

但是，没有一行同时包含 v4 和 v6 地址。（也就是说，记录要么来自机器的 v4 堆栈，要么来自机器的 v6 堆栈。）

回答by Alain Pannetier

In Oracle, what is the appropriate data type or technique for representing network addresses, which addresses may be IPv4 or IPv6

在 Oracle 中，表示网络地址的适当数据类型或技术是什么，哪些地址可以是 IPv4 或 IPv6

There are two approaches :

有两种方法：

  1. storing only.
  2. storing the conventional representation
  1. 仅存储。
  2. 存储常规表示

For storing only. An IPV4 address should be an integer (32bits are enough). For IP V6, 128 bits, INTEGER (which is similar to Number(38)) will do. Of course, that's storing. That approach takes the view that the representation is a matter for the application.

仅用于存储。IPV4 地址应该是一个整数（32 位就足够了）。对于 IP V6，128 位，INTEGER（类似于 Number(38)）就可以了。当然，这是存储。该方法认为表示是应用程序的问题。

If one take the opposite strategy, of storing the conventional representation, one needs to make sure that IP V4 and IPV6 addresses have only one conventional (string) representation. It's well-known for ipV4. As for IPV6, there is also a standard format.

如果采取相反的策略，即存储常规表示，则需要确保 IP V4 和 IPV6 地址只有一种常规（字符串）表示。它以ipV4而闻名。至于IPV6，也有标准格式。

My preference goes to the first strategy. In the worst case, you can adopt an hybrid approach (non acid though) and store both the binary and the ascii representation side by side with "priority" to the binary value.

我更喜欢第一种策略。在最坏的情况下，您可以采用混合方法（尽管是非酸）并将二进制和 ascii 表示并排存储，并且“优先”于二进制值。

No row contains both v4 and v6 addresses, however.

但是，没有一行同时包含 v4 和 v6 地址。

The standard representation of a IPV4 address in IPV6 format is : ::ffff:192.0.2.128.

IPV6 格式的 IPV4 地址的标准表示是：::ffff:192.0.2.128。

I don't know the context but I would however reserve 2 columns, one for IPV4 and the other for a distinct ipV6 address.

我不知道上下文，但我会保留两列，一列用于 IPV4，另一列用于不同的 ipV6 地址。

Update
Following a good comment by @sleepyMonad's, I'd like to point out that instead of the Numberdata type it is preferable to use the INTEGER data type, which will happily accommodate the highest possible value that can be expressed with a 128 bits integer 'ff...ff' (which would need 39decimal digits). 38 is the highest power of ten ranging from 0 to 9that can be encoded on 128 bits but one can still insert the maximum unsigned value for 2**128 - 1(decimal 340282366920938463463374607431768211455). Here is a small test to illustrate this possibility.

更新
根据@sleepyMonad 的一个很好的评论，我想指出，最好使用 INTEGER 数据类型而不是Number数据类型，它会很高兴地容纳可以用 128 位整数表示的最高可能值'ff...ff'（需要39 个十进制数字）。38 是从 0 到 9的 10 的最高幂，可以在 128 位上进行编码，但仍然可以插入2**128 - 1的最大无符号值（十进制 340282366920938463463374607431768211455）。这里有一个小测试来说明这种可能性。

create table test (
  id integer primary key,
  ipv6_address_bin INTEGER );

-- Let's enter 2**128 - 1 in the nueric field
insert into test (id, ipv6_address_bin) values ( 1, to_number ( 'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF', 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX') ) ;

-- retrieve it to make sure it's not "truncated".
select to_char ( ipv6_address_bin, 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX' ) from test where id = 1 ;
-- yields 'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF'

select to_char ( ipv6_address_bin ) from test where id = 1 ;
-- yields 340282366920938463463374607431768211455

select LOG(2, ipv6_address_bin) from test where id = 1 ;
-- yields 128

select LOG(10, ipv6_address_bin) from test where id = 1 ;
-- yields > 38

回答by Branko Dimitrijevic

Store it in RAW.

将其存储在 RAW 中。

RAW is variable-length byte array, so....

RAW 是变长字节数组，所以....

  • just treat the IPv4 as an array of 4 bytes
  • and IPv6 as an array of 16 bytes
  • 只需将 IPv4 视为 4 个字节的数组
  • 和 IPv6 作为 16 个字节的数组

...and store either one of them in directly in RAW(16).

...并将其中之一直接存储在 RAW(16) 中。

RAW can be indexed, be a PK, UNIQUE or FOREIGN KEY, so you can do anything you normally could with VARCHAR2 or INT/NUMBER/DECIMAL, but with less conversion and storage overhead.

RAW 可以被索引，可以是 PK、UNIQUE 或 FOREIGN KEY，因此您可以使用 VARCHAR2 或 INT/NUMBER/DECIMAL 执行通常可以执行的任何操作，但转换和存储开销较少。

To illustrate the storage overhead of INT over RAW, consider the following example:

为了说明 INT 对 RAW 的存储开销，请考虑以下示例：

CREATE TABLE IP_TABLE (
    ID INT PRIMARY KEY,
    IP_RAW RAW(16), 
    IP_INT INT
);

INSERT INTO IP_TABLE (ID, IP_RAW, IP_INT) VALUES (
    1,
    HEXTORAW('FFFFFFFF'),
    TO_NUMBER('FFFFFFFF', 'XXXXXXXX')
);

INSERT INTO IP_TABLE (ID, IP_RAW, IP_INT) VALUES (
    2,
    HEXTORAW('FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF'),
    TO_NUMBER('FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF', 'XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX')
);

SELECT VSIZE(IP_RAW), VSIZE(IP_INT), IP_TABLE.*  FROM IP_TABLE;

The result (under Oracle 10.2):

结果（在 Oracle 10.2 下）：

table IP_TABLE created.
1 rows inserted.
1 rows inserted.
VSIZE(IP_RAW)          VSIZE(IP_INT)          ID                     IP_RAW                           IP_INT                 
---------------------- ---------------------- ---------------------- -------------------------------- ---------------------- 
4                      6                      1                      FFFFFFFF                         4294967295             
16                     21                     2                      FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF 340282366920938463463374607431768211455

回答by Alexander Hartmaier

@Alain Pannetier (because I can't comment yet): The ANSI INTEGER datatype maps to NUMBER(38) in Oracle according to http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements001.htm#i54335. Below the table you find the info that NUMBER only provides 126bit binary precision which is not enought for a 128bit IPv6 address. The maximum value might store fine but there will be addresses that are rouned to the next lower one.

@Alain Pannetier（因为我还不能评论）：根据http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements001，ANSIINTEGER 数据类型映射到 Oracle 中的 NUMBER(38) .htm#i54335。在表格下方，您可以找到 NUMBER 仅提供 126 位二进制精度的信息，这对于 128 位 IPv6 地址来说是不够的。最大值可能存储得很好，但会有一些地址被排到下一个较低的地址。

The internal numeric format is ROUND((length(p)+s)/2))+1 (http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/datatype.htm#i16209).

内部数字格式为 ROUND((length(p)+s)/2))+1 ( http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/datatype.htm#i16209) .

Update:After fiddling around with the issue again I've now found a solution that allows high performance querying of networks that contain an IPv6 address: store the IPv6 addresses and subnet masks in RAW(16) columns and compare them using UTL_RAW.BIT_AND:

更新：再次摆弄这个问题后，我现在找到了一个允许对包含 IPv6 地址的网络进行高性能查询的解决方案：将 IPv6 地址和子网掩码存储在 RAW(16) 列中，并使用 UTL_RAW.BIT_AND 比较它们：

SELECT name, DECODE(UTL_RAW.BIT_AND('20010DB8000000000000000000000001', ipv6_mask), ipv6_net, 1, 0)
FROM ip_net
WHERE ipv6_net IS NOT NULL;

回答by ShoeLace

you could also use a custom oracle object.

您还可以使用自定义 oracle 对象。

SQL>set SERVEROUTPUT on
SQL>drop table test;

Table dropped.

SQL>drop type body inaddr;

Type body dropped.

SQL>drop type inaddr;

Type dropped.

SQL>create type inaddr as object
  2  ( /* TODO enter attribute and method declarations here */
  3  A number(5),
  4  B number(5),
  5  C number(5),
  6  D number(5),
  7  E number(5),
  8  F number(5),
  9  G number(5),
 10  H NUMBER(5),
 11  MAP MEMBER FUNCTION display RETURN VARCHAR2,
 12  MEMBER FUNCTION toString( SELF IN INADDR , CONTRACT BOOLEAN DEFAULT TRUE) RETURN VARCHAR2,
 13  CONSTRUCTOR FUNCTION INADDR(SELF IN OUT NOCOPY INADDR, INADDRASSTRING VARCHAR2)  RETURN SELF AS RESULT
 14  
 15  ) NOT FINAL;
 16  /

SP2-0816: Type created with compilation warnings

SQL>
SQL>
SQL>CREATE TYPE BODY INADDR AS
  2  
  3  MAP MEMBER FUNCTION display RETURN VARCHAR2
  4  IS BEGIN
  5  return tostring(FALSE);
  6  END;
  7  
  8  
  9  MEMBER FUNCTION TOSTRING( SELF IN  INADDR , CONTRACT BOOLEAN DEFAULT TRUE) RETURN VARCHAR2 IS
 10  IP4 VARCHAR2(6) := 'FM990';
 11  ip6 varchar2(6) := 'FM0XXX';
 12    BEGIN
 13  IF CONTRACT THEN
 14    ip6 := 'FMXXXX';
 15  end if;
 16  
 17  IF CONTRACT AND A =0 AND B=0 AND C = 0 AND D=0 AND E =0 AND F = 65535 THEN --ipv4
 18      RETURN  '::FFFF:'||TO_CHAR(TRUNC(G/256),'FM990.')||TO_CHAR(MOD(G,256),'FM990.')||TO_CHAR(TRUNC(H/256),'FM990.')||TO_CHAR(MOD(H,256),'FM990');
 19  ELSE
 20      RETURN
 21  TO_CHAR(A,ip6)||':'||
 22  TO_CHAR(B,IP6)||':'||
 23  TO_CHAR(C,ip6)||':'||
 24  TO_CHAR(D,ip6)||':'||
 25  TO_CHAR(E,ip6)||':'||
 26  TO_CHAR(F,ip6)||':'||
 27  TO_CHAR(G,ip6)||':'||
 28  TO_CHAR(H,ip6);
 29  end if;
 30    end;
 31  
 32      CONSTRUCTOR FUNCTION inaddr(SELF IN OUT NOCOPY inaddr, inaddrasstring VARCHAR2)
 33                                 RETURN SELF AS RESULT IS
 34      begin
 35          if instr(inaddrasstring,'.') > 0 then
 36            --ip4
 37  null;
 38              a := 0;
 39              B := 0;
 40              C := 0;
 41              D := 0;
 42              E := 0;
 43              F := TO_NUMBER('FFFF', 'XXXX');
 44              G := TO_NUMBER(TO_CHAR(TO_NUMBER(REGEXP_SUBSTR(INADDRASSTRING,'([0-9]{1,3}).',1,1,'i',1),'999'),'FM0X')
 45  ||TO_CHAR(TO_NUMBER(REGEXP_SUBSTR(INADDRASSTRING,'([0-9]{1,3}).',1,2,'i',1),'999'),'FM0X')
 46  ,'XXXX');
 47              h := TO_NUMBER(TO_CHAR(TO_NUMBER(REGEXP_SUBSTR(INADDRASSTRING,'([0-9]{1,3}).',1,3,'i',1),'999'),'FM0X')
 48  ||TO_CHAR(TO_NUMBER(REGEXP_SUBSTR(INADDRASSTRING,'([0-9]{1,3})',1,4,'i',1),'999'),'FM0X')
 49  ,'XXXX');
 50  
 51          ELSIF instr(inaddrasstring,':') > 0 then
 52              --ip6
 53              a := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,1,'i',1),'XXXX');
 54              b := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,2,'i',1),'XXXX');
 55              c := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,3,'i',1),'XXXX');
 56              d := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,4,'i',1),'XXXX');
 57              E := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,5,'i',1),'XXXX');
 58              f := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,6,'i',1),'XXXX');
 59              g := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,7,'i',1),'XXXX');
 60              H := TO_NUMBER(REGEXP_SUBSTR(inaddrasstring,'([0-9a-fA-F]{1,4})',1,8,'i',1),'XXXX');
 61          end if;
 62  
 63          RETURN;
 64      END;
 65  end;
 66  /

Type body created.

SQL>
SQL>create table test
  2  (id integer primary key,
  3  address inaddr);

Table created.

SQL>
SQL>select * from test;

no rows selected

SQL>
SQL>
SQL>insert into test values (1, INADDR('fe80:0000:0000:0000:0202:b3ff:fe1e:8329') );

1 row created.

SQL>INSERT INTO TEST VALUES (2, INADDR('192.0.2.128') );

1 row created.

SQL>insert into test values (3, INADDR('20.0.20.1') );

1 row created.

SQL>insert into test values (4, INADDR('fe80:0001:0002:0003:0202:b3ff:fe1e:8329') );

1 row created.

SQL>insert into test values (5, INADDR('fe80:0003:0002:0003:0202:b3ff:fe1e:8329') );

1 row created.

SQL>INSERT INTO TEST VALUES (6, INADDR('fe80:0003:0001:0003:0202:b3ff:fe1e:8329') );

1 row created.

SQL>INSERT INTO TEST VALUES (7, INADDR('fe80:0003:0001:0003:0202:b3ff:fe1e:8328') );

1 row created.

SQL>INSERT INTO TEST VALUES (8, INADDR('dead:beef:f00d:cafe:dea1:aced:b00b:1234') );

1 row created.

SQL>
SQL>COLUMN INET_ADDRESS_SHORT FORMAT A40
SQL>column inet_address_full format a40
SQL>
SQL>select t.address.toString() inet_address_short, t.address.display( ) inet_address_full
  2  from test T
  3  order by t.address ;

INET_ADDRESS_SHORT                       INET_ADDRESS_FULL
---------------------------------------- ----------------------------------------
::FFFF:20.0.20.1                         0000:0000:0000:0000:0000:FFFF:1400:1401
::FFFF:192.0.2.128                       0000:0000:0000:0000:0000:FFFF:C000:0280
DEAD:BEEF:F00D:CAFE:DEA1:ACED:B00B:1234  DEAD:BEEF:F00D:CAFE:DEA1:ACED:B00B:1234
FE80:0:0:0:202:B3FF:FE1E:8329            FE80:0000:0000:0000:0202:B3FF:FE1E:8329
FE80:1:2:3:202:B3FF:FE1E:8329            FE80:0001:0002:0003:0202:B3FF:FE1E:8329
FE80:3:1:3:202:B3FF:FE1E:8328            FE80:0003:0001:0003:0202:B3FF:FE1E:8328
FE80:3:1:3:202:B3FF:FE1E:8329            FE80:0003:0001:0003:0202:B3FF:FE1E:8329
FE80:3:2:3:202:B3FF:FE1E:8329            FE80:0003:0002:0003:0202:B3FF:FE1E:8329

8 rows selected.

SQL>spool off

i just put this together in the last hour (and taught myself objects at the same time) so im sure it can be improved upon. if i make updates i'll repost them here

我只是在最后一个小时把它放在一起（并同时自学了对象）所以我相信它可以改进。如果我进行更新，我会在这里重新发布

回答by Nashev

I would prefer store IP addresses just in string, in format, returned by SYS_CONTEXT ('USERENV', 'IP_ADDRESS')

我更喜欢仅以字符串形式存储 IP 地址，格式由 SYS_CONTEXT ('USERENV', 'IP_ADDRESS') 返回

In refference of SYS_CONTEXTin 11g are described only default return value length as 256 bytes and does not described return value size for exacly 'IP_ADDRESS' context.

在11g 中的SYS_CONTEXT 参考中，仅将默认返回值长度描述为 256 字节，并没有描述精确的“IP_ADDRESS”上下文的返回值大小。

In document Oracle Database and IPv6 Statement of Directiondescribed:

在文档Oracle 数据库和 IPv6 方向声明中描述：

Oracle Database 11g Release 2 supports the standard IPv6 address notations specified by RFC2732. A 128bit IP address is generally represented as 8 groups of 4 hex digits, with the “:” symbol as the group separator. The leading zeros in each group are removed. For example, 1080:0:0:0:8:800:200C:417A would be a valid IPv6 address. One or more consecutive zero fields can optionally be compressed with the “::” separator. For example, 1080::8:800:200C:417A.

Oracle Database 11g 第 2 版支持 RFC2732 指定的标准 IPv6 地址表示法。一个 128 位的 IP 地址一般表示为 8 组 4 位十六进制数字，以“:”符号作为组分隔符。删除每组中的前导零。例如，1080:0:0:0:8:800:200C:417A 将是有效的 IPv6 地址。可以选择使用“::”分隔符压缩一个或多个连续的零字段。例如，1080::8:800:200C:417A。

From this notes I prefer to make column IP_ADDRESS varchar2(39)to allow store 8 group by 4 digits and 7 separators between this groups.

从这个笔记中，我更喜欢使列IP_ADDRESS varchar2(39)允许存储 8 组 4 位数字和这些组之间的 7 个分隔符。

回答by Wernfried Domscheit

The possibilities are:

可能性是：

  • Store as string, i.e. VARCHAR2(example 1080::8:800:200c:417a)
  • Store as numeric value
    • NUMBERdata type
    • INTEGERdata type
  • Store as RAWvalue
    • One RAW value, i.e. RAW(4)or RAW(16)for IPv4 or IPv6 respectively
    • 4 x RAW(1)or 8 x RAW(2)for IPv4 or IPv6 respectively
  • 存储为字符串，即VARCHAR2（示例1080::8:800:200c:417a）
  • 存储为数值
    • NUMBER数据类型
    • INTEGER数据类型
  • 存储为RAW值
    • 一个原始值，即RAW(4)或RAW(16)分别为IPv4或IPv6
    • IPv4 或 IPv6 分别为4 xRAW(1)或 8 xRAW(2)

I would recommend to use RAWvalues because

我建议使用RAW值，因为

  • If you use strings then you have to consider different formats of IPv6. 

    1080::8:800:200C:417A
1080::8:800:200c:417a
1080::8:800:32.12.65.122
1080:0:0:0:8:800:200C:417A
1080:0:0:0:0008:0800:200C:417A
1080:0000:0000:0000:0008:0800:200C:417A

    are all legal representations of the same IPv6 IP-Address. Your application needs to enforce a common format for proper usage, e.g. use in WHEREcondition.

  • NUMBER/INTEGERvalues are senseless without conversion to human-readable format. You cannot use INTEGERdata type in PL/SQL

    i INTEGER := 2**128-1; -- i.e. ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

-> ORA-06502: PL/SQL: numeric or value error: number precision too large.

  • In case you have to work with subnetting you cannot use function BITAND- it also supports numbers only up to 2^127

  • You can use UTL_RAWfunctions UTL_RAW.BIT_AND, UTL_RAW.BIT_COMPLEMENT, UTL_RAW.BIT_ORfor subnet operations.

  • In case you have to deal with really big amountof data (I am talking about billions of rows) it might be beneficial to split the IP-Address into several RAW values, i.e. 4 x RAW(1)or 8 x RAW(2). Such columns would be predestinated for Bitmap-Indexesand you would save a lot of disc space and gain performance.

  • 如果使用字符串，则必须考虑 IPv6 的不同格式。 

    1080::8:800:200C:417A
1080::8:800:200c:417a
1080::8:800:32.12.65.122
1080:0:0:0:8:800:200C:417A
1080:0:0:0:0008:0800:200C:417A
1080:0000:0000:0000:0008:0800:200C:417A

    都是相同 IPv6 IP 地址的法律代表。您的应用程序需要强制使用通用格式才能正确使用，例如在WHERE条件下使用。

  • NUMBER/INTEGER如果不转换为人类可读的格式，值将毫无意义。不能INTEGER在 PL/SQL 中使用数据类型

    i INTEGER := 2**128-1; -- i.e. ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff

-> ORA-06502: PL/SQL: numeric or value error: number precision too large.

  • 如果您必须使用子网划分，则不能使用功能BITAND- 它还支持最多 2^127 的数字

  • 您可以使用UTL_RAW功能UTL_RAW.BIT_AND，UTL_RAW.BIT_COMPLEMENT，UTL_RAW.BIT_OR子网操作。

  • 如果您必须处理非常大量的数据（我说的是数十亿行），将 IP 地址拆分为几个 RAW 值可能会有所帮助，即 4 xRAW(1)或 8 x RAW(2)。此类列将用于位图索引，您将节省大量磁盘空间并提高性能。

回答by Franky Wong

The Oracle documentation does state INTEGER is an alias to NUMBER(38), but that is probably a typo, because the paragraph above it states:

Oracle 文档确实声明 INTEGER 是 NUMBER(38) 的别名，但这可能是一个错字，因为上面的段落指出：

NUMBER(p,s) where: p is the precision... Oracle guarantees the portability of numbers with precision of up to 20 base-100 digits, which is equivalent to 39 or 40 decimal digits depending on the position of the decimal point.

NUMBER(p,s) 其中： p 是精度... Oracle 保证数字的可移植性，精度高达 20 个以 100 为基数的数字，这相当于 39 或 40 个十进制数字，具体取决于小数点的位置。

So NUMBER can store 39 to 40 digits, and INTEGER is likely an alias to NUMBER(max precision) instead of NUMBER(38). There is why the example provided works (and it works if you change INTEGER to NUMBER).

所以 NUMBER 可以存储 39 到 40 位数字，INTEGER 很可能是 NUMBER(max precision) 而不是 NUMBER(38) 的别名。这就是提供的示例有效的原因（如果您将 INTEGER 更改为 NUMBER，它也有效）。

相关推荐

我应该使用哪种 JDBC 驱动程序类型来访问 Oracle 数据库？

我应该使用哪种 JDBC 驱动程序类型来访问 Oracle 数据库？

oracle 有条件地定义一个游标

oracle 有条件地定义一个游标

oracle PL/SQL 字符串任务

oracle PL/SQL 字符串任务

Oracle RAC 和序列

Oracle RAC 和序列

相关推荐
最近更新
标签