Unix Technical Forum

SEO

vBulletin Search Engine Optimization


Go Back   Unix Technical Forum > Database Server Software > Oracle Database

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 02-26-2008, 07:48 AM
monesseldeur
 
Posts: n/a
Default store result of query in variable

Hi all,

I'm trying to write a script in which I need the result of a query to
perform an insert in a table.

Something like this:

var = select max(Xid) from tbl_X;
var = var + 1;
insert into tbl_X (Xid) values (var);

Is this possible without uising Pl/SQL?
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 02-26-2008, 07:48 AM
DA Morgan
 
Posts: n/a
Default Re: store result of query in variable

monesseldeur wrote:
> Hi all,
>
> I'm trying to write a script in which I need the result of a query to
> perform an insert in a table.
>
> Something like this:
>
> var = select max(Xid) from tbl_X;
> var = var + 1;
> insert into tbl_X (Xid) values (var);
>
> Is this possible without uising Pl/SQL?


Yes.

But far more likely to create problems.

Is this a school assignment?
--
Daniel A. Morgan
Oracle Ace Director & Instructor
University of Washington
damorgan@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 02-26-2008, 07:48 AM
monesseldeur
 
Posts: n/a
Default Re: store result of query in variable

On 4 dec, 09:03, DA Morgan <damor...@psoug.org> wrote:
> monesseldeur wrote:
> > Hi all,

>
> > I'm trying to write a script in which I need the result of a query to
> > perform an insert in a table.

>
> > Something like this:

>
> > var = select max(Xid) from tbl_X;
> > var = var + 1;
> > insert into tbl_X (Xid) values (var);

>
> > Is this possible without uising Pl/SQL?

>
> Yes.
>
> But far more likely to create problems.
>
> Is this a school assignment?
> --
> Daniel A. Morgan
> Oracle Ace Director & Instructor
> University of Washington
> damor...@x.washington.edu (replace x with u to respond)
> Puget Sound Oracle Users Groupwww.psoug.org


No, a work assignment ;-))

It is used as an installationscript, thus only run once.

How can it be done?
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #4 (permalink)  
Old 02-26-2008, 07:48 AM
mk
 
Posts: n/a
Default Re: store result of query in variable

On 4 ΔΕΛ, 10:47, monesseldeur <raymondesseld...@gmail.com> wrote:
> Hi all,
>
> I'm trying to write a script in which I need the result of a query to
> perform an insert in a table.
>
> Something like this:
>
> var = select max(Xid) from tbl_X;
> var = var + 1;
> insert into tbl_X (Xid) values (var);
>
> Is this possible without uising Pl/SQL?


insert into tbl_X (Xid)
select max(Xid)+1 from tbl_X
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #5 (permalink)  
Old 02-26-2008, 07:48 AM
fitzjarrell@cox.net
 
Posts: n/a
Default Re: store result of query in variable

On Dec 4, 1:47 am, monesseldeur <raymondesseld...@gmail.com> wrote:
> Hi all,
>
> I'm trying to write a script in which I need the result of a query to
> perform an insert in a table.
>
> Something like this:
>
> var = select max(Xid) from tbl_X;
> var = var + 1;
> insert into tbl_X (Xid) values (var);
>
> Is this possible without uising Pl/SQL?


Certainly, but it's not the brightest of ideas. From one session I
ran this:

SQL> @insert_w_var
SQL> --
SQL> -- Create test table
SQL> --
SQL> create table ins_test(keycol number, keyval varchar2(20));

Table created.

SQL>
SQL> --
SQL> -- Add primary key constraint
SQL> --
SQL> alter table ins_test add constraint ins_test_pk primary key
(keycol);

Table altered.

SQL>
SQL> --
SQL> -- Insert data
SQL> --
SQL> insert all
2 into ins_test
3 (keycol, keyval)
4 values
5 (1, 'First value')
6 into ins_test
7 (keycol, keyval)
8 values
9 (2, 'Second value')
10 into ins_test
11 (keycol, keyval)
12 values
13 (3, 'Third value')
14 into ins_test
15 (keycol, keyval)
16 values
17 (4, 'Fourth value')
18 into ins_test
19 (keycol, keyval)
20 values
21 (5, 'Fifth value')
22 into ins_test
23 (keycol, keyval)
24 values
25 (6, 'Sixth value')
26 select * from dual;

6 rows created.

SQL>
SQL> --
SQL> -- Commit changes
SQL> --
SQL> commit;

Commit complete.

SQL>
SQL> --
SQL> -- Start questionable process to
SQL> -- insert more data based upon
SQL> -- current max(keycol) value
SQL> --
SQL>
SQL> --
SQL> -- Set a variable to reuse the returned
SQL> -- max value
SQL> --
SQL> --
SQL> -- Rather dumb idea as the max() from
SQL> -- any query will miss any new values
SQL> -- inserted by other sessions and not
SQL> -- yet committed
SQL> --
SQL> column maxval new_value next_key
SQL>
SQL> --
SQL> -- Return current max(keycol)
SQL> --
SQL> -- Not reliable in the least
SQL> -- unless there is only one user
SQL> -- ever on the system, and it's
SQL> -- you
SQL> --
SQL> select max(keycol) maxval from ins_test;


MAXVAL
----------

6

SQL>
SQL> --
SQL> -- Use the saved value for the next insert
SQL> --
SQL> -- Not a good idea
SQL> --
SQL> -- Using a sequence and a trigger is far
SQL> -- more reliable and recommended
SQL> --
SQL> insert into ins_test (keycol, keyval)
2 values (&next_key + 1, 'Next value in line');
old 2: values (&next_key + 1, 'Next value in line')
new 2: values ( 6 + 1, 'Next value in line')

1 row created.

SQL>
SQL> --
SQL> -- Wait for a minute so a second insert of this
SQL> -- same type can occur from a different session
SQL> --
SQL>
SQL> exec dbms_lock.sleep(60);

PL/SQL procedure successfully completed.

SQL>
SQL> --
SQL> -- Commit the changes, or try to
SQL> --
SQL> commit;

Commit complete.

SQL>
SQL> spool off

While in the midst of that dbms_lock.sleep call I ran this from a
second session:

SQL> @ins_w_var_second_sess
SQL> --
SQL> -- Start questionable process to
SQL> -- insert more data based upon
SQL> -- current max(keycol) value
SQL> --
SQL>
SQL> --
SQL> -- Set a variable to reuse the returned
SQL> -- max value
SQL> --
SQL> --
SQL> -- Rather dumb idea as the max() from
SQL> -- any query will miss any new values
SQL> -- inserted by other sessions and not
SQL> -- yet committed
SQL> --
SQL> column maxval new_value next_key
SQL>
SQL> --
SQL> -- Return current max(keycol)
SQL> --
SQL> -- Not reliable in the least
SQL> -- unless there is only one user
SQL> -- ever on the system, and it's
SQL> -- you
SQL> --
SQL> select max(keycol) maxval from ins_test;


MAXVAL
----------

6

SQL>
SQL> --
SQL> -- Use the saved value for the next insert
SQL> --
SQL> -- Not a good idea
SQL> --
SQL> -- Using a sequence and a trigger is far
SQL> -- more reliable and recommended
SQL> --
SQL> insert into ins_test (keycol, keyval)
2 values (&next_key + 1, 'Next value in line');
old 2: values (&next_key + 1, 'Next value in line')
new 2: values ( 6 + 1, 'Next value in line')
insert into ins_test (keycol, keyval)
*
ERROR at line 1:
ORA-00001: unique constraint (BING.INS_TEST_PK) violated


SQL>
SQL> --
SQL> -- Wait for a minute so a second insert of this
SQL> -- same type can occur from a different session
SQL> --
SQL>
SQL> exec dbms_lock.sleep(60);

PL/SQL procedure successfully completed.

SQL>
SQL> --
SQL> -- Commit the changes, or try to
SQL> --
SQL> commit;

Commit complete.

SQL>
SQL> spool off

Notice the SAME max(key_col) appears, even after I've inserted a new
value in the table, because the first insert hasn't committed. Also,
which you can't see, was the effect of session #2 being locked and
waiting while the dbms_lock.sleep(60) call finished in session #1.
Your 'process' doesn't scale well at all, and it doesn't behave as you
might expect. Again, it's not the brightest idea.

The accepted manner to do this is to use an ordered sequence and a
trigger, such that any session can insert into the table and not
provide conflicting values for the key column or columns:

SQL> @insert_w_trig
SQL> --
SQL> -- Create test table
SQL> --
SQL> create table ins_test(keycol number, keyval varchar2(20));

Table created.

SQL>
SQL> --
SQL> -- Add primary key constraint
SQL> --
SQL> alter table ins_test add constraint ins_test_pk primary key
(keycol);

Table altered.

SQL>
SQL> --
SQL> -- Add a sequence, and a trigger, to populate the key column
SQL> --
SQL> create sequence ins_test_seq
2 start with 1
3 increment by 1
4 nomaxvalue
5 nocycle
6 order;

Sequence created.

SQL>
SQL> create or replace trigger pop_ins_test_pk
2 before insert on ins_test
3 for each row
4 begin
5 select ins_test_seq.nextval
6 into :new.keycol
7 from dual;
8 end;
9 /

Trigger created.

SQL>
SQL> --
SQL> -- Insert data
SQL> --
SQL> insert all
2 into ins_test
3 (keyval)
4 values
5 ('First value')
6 into ins_test
7 (keyval)
8 values
9 ('Second value')
10 into ins_test
11 (keyval)
12 values
13 ('Third value')
14 into ins_test
15 (keyval)
16 values
17 ('Fourth value')
18 into ins_test
19 (keyval)
20 values
21 ('Fifth value')
22 into ins_test
23 (keyval)
24 values
25 ('Sixth value')
26 select * from dual;

6 rows created.

SQL>
SQL> --
SQL> -- Commit changes
SQL> --
SQL> commit;

Commit complete.

SQL>
SQL> insert into ins_test (keyval)
2 values ('Next value in line');

1 row created.

SQL>
SQL> --
SQL> -- Wait for a minute so a second insert of this
SQL> -- same type can occur from a different session
SQL> --
SQL>
SQL> exec dbms_lock.sleep(60);

PL/SQL procedure successfully completed.

SQL>
SQL> --
SQL> -- Commit the changes, or try to
SQL> --
SQL> commit;

Commit complete.

SQL>
SQL> select * from ins_test;

KEYCOL
KEYVAL
----------
--------------------
8 Next value in
line
1 First
value
2 Second
value
3 Third
value
4 Fourth
value
5 Fifth
value
6 Sixth
value
7 Next value in
line

8 rows selected.

SQL> spool off

And, from a second session inserting at the same time:

SQL> @ins_w_trig_second_sess
SQL> --
SQL> -- Using a sequence and a trigger is far
SQL> -- more reliable and recommended
SQL> --
SQL> insert into ins_test (keyval)
2 values ('Next value in line');

1 row created.

SQL>
SQL> --
SQL> -- Wait for a minute so a second insert of this
SQL> -- same type can occur from a different session
SQL> --
SQL>
SQL> exec dbms_lock.sleep(60);

PL/SQL procedure successfully completed.

SQL>
SQL> --
SQL> -- Commit the changes, or try to
SQL> --
SQL> commit;

Commit complete.

SQL>
SQL> select * from ins_test;

KEYCOL
KEYVAL
----------
--------------------
8 Next value in
line
1 First
value
2 Second
value
3 Third
value
4 Fourth
value
5 Fifth
value
6 Sixth
value
7 Next value in
line

8 rows selected.

SQL> spool off

Note there were no problems with either insert 'hanging' due to the
data changes not being committed, and no constraint violations do to
an erroneous select strategy.

To answer your question, yes, it CAN be done, sort of. But, I
wouldn't recommend it. Ever.


David Fitzjarrell
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #6 (permalink)  
Old 02-26-2008, 07:48 AM
gazzag
 
Posts: n/a
Default Re: store result of query in variable

On 4 Dec, 07:47, monesseldeur <raymondesseld...@gmail.com> wrote:
> Hi all,
>
> I'm trying to write a script in which I need the result of a query to
> perform an insert in a table.
>
> Something like this:
>
> var = select max(Xid) from tbl_X;
> var = var + 1;
> insert into tbl_X (Xid) values (var);
>
> Is this possible without uising Pl/SQL?


Have you considered a database sequence?

http://download.oracle.com/docs/cd/B....htm#sthref883

HTH

-g
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #7 (permalink)  
Old 02-26-2008, 07:48 AM
Vince
 
Posts: n/a
Default Re: store result of query in variable

On Dec 3, 11:47 pm, monesseldeur <raymondesseld...@gmail.com> wrote:
> Hi all,
>
> I'm trying to write a script in which I need the result of a query to
> perform an insert in a table.
>
> Something like this:
>
> var = select max(Xid) from tbl_X;
> var = var + 1;
> insert into tbl_X (Xid) values (var);
>
> Is this possible without uising Pl/SQL?


How about:
insert into tbl_X(Xid)
select max(Xid) + 1 from tbl_X;

As others have pointed out, you probably want to look into sequences.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


All times are GMT. The time now is 02:32 AM.


Powered by vBulletin® Version 3.6.5
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
SEO by vBSEO 3.2.0
UnixAdminTalk.com

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776