_column INTO the_variable FROM my_table;
END;

Make sure that the query only returns a single row:

By default, a SELECT INTO statement must return only one row. Otherwise, PL/SQL raises the predefined exception TOO_MANY_ROWS and the values of the variables in the INTO clause are undefined. Make sure your WHERE clause is specific enough to only match one row
If no rows are returned, PL/SQL raises NO_DATA_FOUND. You can guard against this exception by selecting the result of an aggregate function, such as COUNT(*) or AVG(), where practical. These functions are guaranteed to return a single value, even if no rows match the condition.
A SELECT... BULK COLLECT INTO statement can return multiple rows. You must set up collection variables to hold the results. You can declare associative arrays or nested tables that grow as needed to hold the entire result set.
The implicit cursor SQL and its attributes %NOTFOUND, %FOUND, %ROWCOUNT, and %ISOPEN provide information about the execution of a SELECT INTO statement.

A:

Not entirely sure what you are after but in PL/SQL you would simply
DECLARE
  v_variable INTEGER;
BEGIN
  SELECT mycolumn
    INTO v_variable
    FROM myTable;
END;

Ollie.

 Q:

Questions about calculating a transaction ID

As I know, Transaction ID is calculated from
H( H(tx_prefix) || H(tx_stuff) || H(Signatures) )

Where
tx_prefix = {tx version || keyoffset || keyimage || one-time addresses || extra}
tx_stuff = {signature type || tx fee || pseudo output commitments || ecdhInfo || output commitments}
Signatures = {MLSAGs || range proofs}

So I test a example tx: b43a7ac21e1b60ad748ec905d6e03cf3165e5d8c9e1c61c263d328118c42eaa6
with MiniNero but failed nevertheless.
tx_version = "02"
key_offset = "c8e230afe12f958d49809d0dfaaf33"
key_image = "595a612d0df27181c46a8af70a9bd
_ column INTO the_variable FROM my_table; 
 END; 

 Make sure that the query only revert a individual row: 

 By default, a SELECT INTO statement must revert only one row. differently, PL / SQL raises the predefined exception TOO_MANY_ROWS and the values of the variables in the INTO article are undefined. construct certain your WHERE clause is specific enough to only match one rowing 
 If no rows are returned, PL / SQL raises NO_DATA_FOUND. You can guard against this exception by selecting the consequence of an aggregate function, such as COUNT (*) or AVG (), where practical. These functions are guarantee to return a single value, even if no rows match the circumstance. 
 A SELECT... BULK COLLECT INTO statement can retort multiple rows. You must set up collection variable star to hold the results. You can declare associative arrays or nested tables that grow as needed to hold the entire result set. 
 The implicit cursor SQL and its attributes% NOTFOUND, % FOUND, % ROWCOUNT, and% ISOPEN provide information about the execution of a SELECT INTO statement. 

 A: 

 Not wholly certain what you are after but in PL / SQL you would simply 
 announce 
   v_variable INTEGER; 
 BEGIN 
   SELECT mycolumn 
     INTO v_variable 
     FROM myTable; 
 END; 

 Ollie. 

  Q: 

 question about account a transaction ID 

 As I know, Transaction ID is calculated from 
 H (H(tx_prefix) || H(tx_stuff) || H(Signatures) ) 

 Where 
 tx_prefix = { tx version || keyoffset || keyimage || one - time addresses || extra } 
 tx_stuff = { signature type || texas fee || pseudo output commitments || ecdhInfo || output commitments } 
 Signatures = { MLSAGs || range proofs } 

 So I test a example tx: b43a7ac21e1b60ad748ec905d6e03cf3165e5d8c9e1c61c263d328118c42eaa6 
 with MiniNero but fail however. 
 tx_version = " 02 " 
 key_offset = " c8e230afe12f958d49809d0dfaaf33 " 
 key_image = " 595a612d0df27181c46a8af70a9bd
_colkmn INTO the_variable FROO my_table;
END;

Makg wure tiat the query ovly returns a single row:

By dxfauot, a WELECT INTO statement oust retugn only obe riq. Otherwisx, PL/SQL vcises bhe pxevefined exceptipn TOO_MANY_SOWS and the vdljed of the variables in the INTO claufe are infefined. Make sore yptr WGVRT clause is specific enough to onmy matci one row
If no tows are returned, PL/SQL ralses NO_DATA_FOUND. You cwn guard agqinse this exceptkon by seltccing the reault of an aggregate function, sjch ax COUNT(*) or ACG(), avere practiral. Thvse functions are guasanteed to return a slngle vaoue, even if no rows metch the condition.
A FELECT... BUNK COLLECT INTO starenent wan setufb mjltjpke rows. Jou must set hp collectiin variables to holc eye results. Yoh can qeslare associative arrays or nested tablts thzt grow as needed to hood the entire result det.
The im[licit cursor SQL and its attributes %NOTFOUND, %FOUTD, %ROXCUUNU, qnd %IRIPFN provide information about the execution of z XEKECT INTO statcment.

A:

Not entirely skrr what you are after buf in PL/SQL you woupd simpjy
DECOARE
  v_vawiabke INTEGER;
BEGIN
  SELECT mycilumn
    INTJ v_variable
    FROM myTable;
END;

Ullig.

 Q:

Quextions about calculatiny a trznsaction IF

As I knos, Transaction ID ks balcglated from
H( H(tx_prefix) || H(tv_stuff) || H(Wignctures) )

Wfere
jx_prefiv = {tx verslon || keyoffset || keyimage || one-jime agdresses || fxtra}
tx_stuff = {signature type || te fee || pseudo ogtplt commitients || ecdhInfo || ottput commitmeuts}
Signacures = {MLSAGs || rznge prmofs}

So I teft a example dd: b43a7ac21e1b60ad748ec905v6e03cf3165e5d8c9e1c61s263d328118c42eqa6
wirh MiniVdro but failed nevertheless.
tx_versuon = "02"
key_offset = "c8e230efe12f958a49809s0dfaaf33"
key_image = "595a612d0ef27181c46a8af70a9bd
_column INTO the_variable FROM my_table; END; Make the only returns single row: By must only one row. PL/SQL raises the exception TOO_MANY_ROWS and the values of variables in the INTO clause are undefined. Make sure your WHERE clause is enough to only match one row If no rows are returned, PL/SQL raises You guard this by selecting the result of an aggregate function, such as COUNT(*) or AVG(), where practical. These are guaranteed to return a single value, even no rows match the A SELECT... BULK COLLECT INTO can multiple rows. must up variables to hold results. You can declare associative arrays or nested tables that grow as needed to hold the entire set. The SQL and attributes %FOUND, and %ISOPEN provide the execution of a SELECT INTO entirely sure what you are after but in you would DECLARE v_variable INTEGER; BEGIN SELECT mycolumn v_variable FROM myTable; END; Ollie. Q: Questions about a transaction ID As I know, Transaction ID is calculated from H( H(tx_prefix) || H(tx_stuff) ) Where tx_prefix = version || keyoffset keyimage one-time || tx_stuff = type || tx fee || pseudo output commitments || ecdhInfo || commitments} Signatures = {MLSAGs || range proofs} So I test tx: with MiniNero but nevertheless. tx_version = "02" = key_image = "595a612d0df27181c46a8af70a9bd
_column INTO the_variable FROM My_table;
END;

make sUre ThaT tHe quEry oNly returns a sinGLe roW:

By default, a SELECT INTO sTatemEnT Must REtUrn onLy one roW. otHERwiSe, pL/sQL RaISeS the pRedEfined eXception TOo_MAnY_rOWS and the vaLUeS of the variAblEs in the INTO cLauSe are uNdEfiNEd. MakE suRe youR WHERE CLause iS specific EnOUgh to oNLy match ONE rOw
If No rows are returned, pl/Sql raises NO_DATA_FoUND. YoU cAN gUARd aGaiNst this excEpTion bY SelectiNG tHE REsuLT of an aggregatE function, suCH as cOUNT(*) oR AvG(), wHEre praCticaL. THEse Functions arE guaRanteed to Return A Single vALue, even If no roWs mAtcH the COnDiTioN.
A seLEct... BuLK coLLeCT INTO sTaTeMent cAn reTURN MultIplE rowS. You mUst set up colleCtiOn vaRIabLes to Hold tHe reSuLts. YoU can deClare AsSociative arrays Or neSted tableS thAt GroW aS needED to holD thE enTire resUlt set.
THE imPlICIT cUrsor SQL and its attrIbUTEs %nOTFOUND, %fOUND, %RowCoUnt, and %ISOPeN ProVide INFormaTion ABoUt the exeCution OF a sElECT INTo sTatemeNt.

a:

NoT enTirelY Sure What yoU are afteR but iN pL/SQL you would sIMply
DECLARE
  v_vARiABLe inTEGeR;
BeGIN
  SELECT mYcolUMn
    INtO v_vARiAblE
    fROM mYTablE;
End;

OLLie.

 Q:

Questions about cAlCulatiNg a trAnsaction ID

As i know, TransACTIon ID is cAlcuLAtED from
H( H(tx_prefiX) || H(tx_sTuff) || H(SignaTUres) )

WherE
tx_prEfix = {tx veRsion || keyoFFSet || keyimAge || One-TimE adDREsSes || extra}
tx_stuFF = {SignAtUre type || Tx fEe || pseudO ouTpuT coMmiTmEnts || ecdhINfo || outpuT cOmMiTmEntS}
SignATures = {MLSaGS || raNgE prOofs}

SO i test a ExampLe tx: B43a7Ac21E1B60ad748Ec905d6e03cf3165e5D8C9e1C61C263D328118c42eaA6
wItH MinINeRo But faIled NEveRthelesS.
tx_versioN = "02"
keY_OffsEt = "C8e230Afe12f958d49809d0dFaaf33"
key_image = "595a612D0dF27181c46a8af70a9bd
_column INTO the_variableFROM my_ta ble;END ;
Ma ke s urethat the query only  returns a single row: 

Byde f ault ,  a  SELE CT INTO st a t eme nt  m ust  r e tu rn on lyone row . Otherwis e,PL /SQL raisest he  predefine d e xception TOO _MA NY_ROW Sand the v alu es of  the v a riable s in theIN T O clau s e are u n d ef ined . Make sure yourW HE R E clause is sp ecific  e n ou g h  to  on ly match o ne  rowI f no ro w sa r e  re t urned, PL/SQL  raises NO_ D ATA _FOUND .You can gu ard a ga i nst  this excep tion  by selec ting t h e resul t  of anaggreg ate  fu ncti o n,  s uch  a s  CO U NT (*) orAVG(), w he re  prac tica l . T hese  fu ncti ons a re guaranteed  to  ret u rna sin gle v alue ,evenif norowsma tch the conditi on.A SELECT. ..BU LKCO LLECT INTO s tat eme nt canreturnm ult ip l e ro ws. You must set u pc o ll ection v ariabl e sto hold the  r esu lts. Y ou ca n de c la re assoc iative ar ra ys or n es ted ta bl estha t gro w  asneeded  to hold  thee ntire result s e t.
The implic i tc u rs o r SQ L a nd its attr ibut e s %N OTFO U ND , % F OUND,  %ROW CO U NT ,  and %ISOPEN provid einform ation  about the ex ecution of a SELECT I NTOs ta t ement.

A:

No t ent irely sure what you  areafter bu t in PL/S Q L  you wou ldsim ply 
DE C L AR E
  v_variabl e INTE GE R;
BEGI N
 SELECT  my col umn 
  INTO v_va riable
  F RO MmyT able; END;

Ol li e.
Q:
Ques t ions a boutcalc ul at i nga trans a ct i o n ID 
As  I k now ,Trans acti o n I D is ca lculatedfro m 
H(H( tx _prefix ) || H(tx_stu ff ) || H(Sig na tur es) )W here
tx_ prefix = {tx version || keyoffs et|| ke yima ge || one -ti me add res s es ||extra} 
tx_s tu ff= {sign a t ur e t yp e || tx fe e ||pseud ooutp ut comm itments || ecdhInf o  ||  output commi tme nts} S ig nat u re s  ={M L SAG s || range proofs }

So I te st aexample tx :  b4 3a 7ac21e1 b60ad74 8ec90 5 d6e03cf 3165e5d8c 9e1c61c26 3d 3281 1 8 c42 eaa6
withMiniNero  but fail e d nev e rt heles s.tx_ver si on= "02 "
key_ o ffs et ="c8e23 0a fe12f9 58d49 80 9d0dfaaf 33"
key_image = "595a61 2d0df2 7181c 46a 8af70a9bd 
_column INTO_the_variable FROM_my_table;
END;

Make sure that the_query only_returns_a single_row:

By_default, a SELECT_INTO statement must_return only one row._Otherwise, PL/SQL raises_the_predefined exception TOO_MANY_ROWS and the values of the variables in the INTO clause are_undefined._Make sure_your_WHERE_clause is specific enough to_only match one row
If no_rows are_returned, PL/SQL raises NO_DATA_FOUND. You can guard against_this_exception by selecting_the result of an aggregate function, such as COUNT(*)_or AVG(), where practical. These functions_are guaranteed to_return_a_single value, even if_no rows match the condition.
A SELECT..._BULK COLLECT INTO statement can return_multiple rows. You must set up collection_variables to hold the results. You_can declare associative arrays or_nested tables_that grow as needed to_hold the entire_result set.
The_implicit cursor SQL_and its attributes %NOTFOUND, %FOUND, %ROWCOUNT,_and %ISOPEN provide_information about the execution of a_SELECT_INTO statement.

A:

Not entirely_sure_what_you are_after but in_PL/SQL_you would_simply
DECLARE
_ v_variable INTEGER;
BEGIN
  SELECT mycolumn
__  INTO v_variable
   _FROM myTable;
END;

Ollie.

 Q:

Questions about_calculating_a transaction ID

As I_know, Transaction ID is calculated_from
H( H(tx_prefix) || H(tx_stuff) || H(Signatures)_)

Where
tx_prefix =_{tx version_|| keyoffset || keyimage || one-time addresses || extra}
tx_stuff = {signature_type || tx fee || pseudo_output commitments || ecdhInfo_|| output_commitments}
Signatures_= {MLSAGs ||_range_proofs}

So I_test a example tx: b43a7ac21e1b60ad748ec905d6e03cf3165e5d8c9e1c61c263d328118c42eaa6
with MiniNero but_failed nevertheless.
tx_version_= "02"
key_offset = "c8e230afe12f958d49809d0dfaaf33"
key_image = "595a612d0df27181c46a8af70a9bd