I am using Oracle 12c Standard Edition.
I accidentally drop the table and try to recover it, but the table does not appear in Recyclebin.
I think the tablespace is due to SYSTEM.
Create table test(
aaa varchar2(20)
....
)
TABLESPACE SYSTEM
STORAGE (
NEXT 1024K
)
/
thank!
Welcome to DBA.SE and thank you for your contribution. You might want to recover the table from your database backup. You do have a backup right? — hot2use21 secs ago
Any idea of why this is so,
CREATE TABLE f AS
SELECT b'000000001' AS a, x'01' AS b;
This creates two columns of
`a` varbinary(2) NOT NULL,
`b` varbinary(1) NOT NULL
However, when I run,
SELECT a=0, b=0, a=b, a<>b FROM f;
+-----+-----+-----+------+
| a=0 | b=0 | a=b | a<>b |
+-----+----...
I'm just wondering because MySQL ENUMs are essentially tied to the table, how do they handle JOINs if two tables have the same ENUM? Are they join based on the ENUM value's or the string-key (input)?
For the follow-up see also, How does MariaDB handle ENUM types used in FOREIGN KEY constraints?
> It's funny - the bug is referenced in the source code, as something that prevents certain unit tests from running. So the development team is clearly aware of this bug.
I am using Oracle 12c Standard Edition.
I accidentally drop the table and try to recover it, but the table does not appear in Recyclebin.
I think the tablespace is due to SYSTEM.
Create table test(
aaa varchar2(20)
....
)
TABLESPACE SYSTEM
STORAGE (
NEXT 1024K
)
/
thank!
Any idea of why this is so,
CREATE TABLE f AS
SELECT b'000000001' AS a, x'01' AS b;
This creates two columns of
`a` varbinary(2) NOT NULL,
`b` varbinary(1) NOT NULL
However, when I run,
SELECT a=0, b=0, a=b, a<>b FROM f;
+-----+-----+-----+------+
| a=0 | b=0 | a=b | a<>b |
+-----+----...
add more temp files. each CPU cores has one tempdb data file, all files should be same size
