meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year |
| seen | Dec 11 '12 at 17:25 | |
| stats | profile views | 10 |
|
May 9 |
awarded | Yearling |
|
Nov 30 |
accepted | Load Numerical Column with Variable Comma |
|
Nov 30 |
comment |
Load Numerical Column with Variable Comma OK, this works; I ended up doing something similar before seeing your answer. I guess, at first, my brain had been looking for a way of using the format model to 'logically' say that the value may or may not contain commas. |
|
Nov 29 |
asked | Load Numerical Column with Variable Comma |
|
Sep 5 |
accepted | Regular Expression Difficulty |
|
Sep 5 |
asked | Regular Expression Difficulty |
|
Aug 30 |
comment |
Using Multi-table Insert for Parent and Child Table @VincentMalgrat: I'm inserting rows returned by a subquery. It is this subquery that determines the parent-child relationship; two insert statements wouldn't work. |
|
Aug 29 |
comment |
Using Multi-table Insert for Parent and Child Table @Phil: Yes I am. |
|
Aug 29 |
asked | Using Multi-table Insert for Parent and Child Table |
|
Aug 27 |
comment |
Limiting Generated Sequence Values in Multi-table Insert clever workaround! |
|
Aug 27 |
accepted | Limiting Generated Sequence Values in Multi-table Insert |
|
Aug 21 |
comment |
Limiting Generated Sequence Values in Multi-table Insert true, I'm not particular about that though. I just constructed this scenario as a MWE. |
|
Aug 21 |
comment |
Limiting Generated Sequence Values in Multi-table Insert What's wrong with mixing currval and 'nextval`? |
|
Aug 21 |
comment |
Limiting Generated Sequence Values in Multi-table Insert By "the most recently generated value but not a new one" I mean the currval of the sequence; I'm not sure what was not understood about that. And, no, I cant afford to do it in PL/SQL. |
|
Aug 21 |
asked | Limiting Generated Sequence Values in Multi-table Insert |
|
Aug 16 |
accepted | FORALL on Nested Collections |
|
Aug 15 |
comment |
FORALL on Nested Collections Wouldn't the third option be most efficient since all inserts are done by means of FORALLs; hence, less context switches? |
|
Aug 14 |
comment |
FORALL on Nested Collections maybe I'll settle for two FORALLs: one for outer_tab and one for inner_tab? |
|
Aug 14 |
asked | FORALL on Nested Collections |
|
Aug 8 |
accepted | Retrieve Indices of Associative Array as Collection |
