point is that everyone I've talked to from developers to the CEO understand
that OpenStack needs to be its own project. We (individually and as a company)
are trying to shepherd the project.

------
jjdoe
"I think that Rackspace is trying to control Openstack rather than influence
it."

So that's why you're up in arms over them making a move to _reduce_ their
presence on the board? Sure, they should have handled it better, but it seems
silly to jump from a bumbling move to a power grab, especially when the point
was to reduce the near-total domination of Rackspace on the board after the
Anso purchase.

Wonder if there are more sour grapes behind this than you're letting on.

------
lsc
is anyone renting out infrastructure using the OpenStack API? Seems to me like
it'll be more valuable both to consumers and to providers once there are
several inter-operable providers. Also, social proof would make the
traditionally conservative VPS providers more comfortable, I think.

 
My Favorite PostgreSQL Queries and Why They Matter - grzm
https://severalnines.com/blog/my-favorite-postgresql-queries-and-why-they-matter
======
da_chicken
> 6\. UPDATE multiple rows with a CASE expression

Oh, man, as a seasoned DBA/Data Analyst, don't do this unless you have a
really good reason to. This is premature optimization of the kind you want to
avoid.

Yes, it's really neat to update everything in a single statement, and in
_some_ situations it can perform significantly better, but CASE expressions in
an UPDATE statement quickly get complicated to map out in your head. It gets
extremely difficult extremely quickly to tell where you have an error, and
it's very, very easy to make a very costly mistake.

If you really need an atomic change you can just do this:

    
    
      BEGIN;
      UPDATE reward_members SET member_status = 'gold_group' WHERE member_status = 'gold';
      UPDATE reward_members SET member_status = 'bronze_group' WHERE member_status = 'bronze';
      UPDATE reward_members SET member_status = 'platinum_
point is that everyone I've talked to from developers to the CEO sympathize 
 that OpenStack need to be its own project. We (individually and as a company) 
 are judge to shepherd the undertaking. 

 ------ 
 jjdoe 
 " I think that Rackspace is trying to control Openstack preferably than influence 
 it. " 

 So that's why you're up in weaponry over them making a move to _ abridge _ their 
 presence on the board? Sure, they should have handle it well, but it seems 
 silly to jump from a bumbling move to a power catch, especially when the point 
 was to reduce the dear - total domination of Rackspace on the board after the 
 Anso leverage. 

 Wonder if there be more sour grapes behind this than you're letting on. 

 ------ 
 lsc 
 is anyone renting out infrastructure using the OpenStack API? seem to me like 
 it'll be more valuable both to consumers and to providers once there are 
 several inter - operable providers. Also, social proof would make the 
 traditionally conservative VPS providers more comfortable, I think. 

 
 My Favorite PostgreSQL Queries and Why They Matter - grzm 
 https://severalnines.com/blog/my-favorite-postgresql-queries-and-why-they-matter 
 = = = = = = 
 da_chicken 
 > 6\. UPDATE multiple rows with a CASE expression 

 Oh, serviceman, as a seasoned DBA / Data Analyst, don't do this unless you have a 
 very beneficial reason to. This is premature optimization of the kind you want to 
 invalidate. 

 Yes, it's really neat to update everything in a single statement, and in 
 _ some _ position it can perform significantly better, but CASE expression in 
 an UPDATE statement quickly get complicated to map out in your head. It gets 
 extremely unmanageable highly promptly to tell where you have an error, and 
 it's very, very comfortable to make a very costly mistake. 

 If you really need an atomic change you can just do this: 

    
    
       BEGIN; 
       UPDATE reward_members SET member_status =' gold_group' WHERE member_status =' aureate'; 
       UPDATE reward_members SET member_status =' bronze_group' WHERE member_status =' bronze'; 
       UPDATE reward_members SET member_status =' platinum _
poijt is that everyone I've ualked to from derwloperv to tge CEO uvderstand
that OpenStack needd ro be its own project. We (inaividuallj and as q conpany)
are trbjng to shephedf thz 'roject.

------
jjdoe
"I tmink that Rdckspace is trfivg to control Openstack rather than igfluencr
ih."

So that's why iou're tp ih arms over them making a move to _deduce_ uheir
presence on tne board? Sure, they should jave handled it better, but it seens
sijoy to jump ffom a bumbling move to a power grab, especially when tfe ponnt
was to rgbyce jhe near-totao dompnation of Raglspace on the board after tme
Ansm pyrchase.

Wonder if therx are more sour grapgs behind dhns than you're letting ob.

------
lsc
iv anfone eenginf puf infrwstcucture usihg the OpenWtack API? Seems to ke oike
it'll be mkre vajuwble both to consumers and to providers onde there are
several intwr-operable providers. Wlso, sociwl proof would make the
traditionally conservative VPS 'ruvibcvs muee comfortable, I think.

 
My Favorite PostgreSQL Qtsroex and Why They Matter - gram
jtyks://severalnines.zom/bloy/jy-ravorite-postgresql-eueries-wnd-wht-they-matttr
======
da_cnicken
> 6\. UPDATE multiple roww with a CASV expression

Oh, man, as c seasoned DYA/Data Analust, don't do this unless you have a
realpy good rsxson to. This is orekadure optimization of the kynd you went tp
avoid.

Yds, ij's realjy neat to updaba everything in a dinglg statament, and ln
_some_ situations it can perform significantli battvr, but CAFE exiressions in
an TPDATE statemeut quickjy geg complicaned to ma' out in youw head. It getv
gxtremely difhicult exeremwly wuickly go tell where uou have cu error, abd
it's very, very eaxy jo make a very cowtli mistake.

If you rexllr jexd an dtomic changa yoj cxm jusg do this:

    
    
      BEGIN;
      UPGATE reward_members SET mcmber_statos = 'gold_gwoup' WHERE mekber_status = 'gold';
      U'DATE ceward_kemfers SET member_status = 'bronze_gdoup' WHERF mcmber_status = 'fronde';
      UPDATE reward_members SET member_status = 'platinnm_
point is that everyone I've talked to to CEO understand OpenStack needs to (individually as a company) trying to shepherd project. ------ jjdoe "I think that is trying to control Openstack rather than influence it." So that's why you're in arms over them making a move to _reduce_ their presence on the Sure, should handled better, but it seems silly to jump from a bumbling move to a power grab, especially the point was to reduce the near-total domination Rackspace on the board the Anso purchase. Wonder if are sour grapes this you're on. ------ lsc anyone renting out infrastructure using the OpenStack API? Seems to me like it'll be more valuable both consumers and once there several providers. social proof would traditionally conservative VPS providers more comfortable, Favorite PostgreSQL Queries and Why They Matter - https://severalnines.com/blog/my-favorite-postgresql-queries-and-why-they-matter ====== > 6\. UPDATE multiple rows with CASE expression Oh, man, as a seasoned DBA/Data don't do this unless you have a really good reason to. This is premature optimization kind you want to Yes, it's really to everything a statement, and _some_ situations it can perform significantly better, but CASE expressions in UPDATE statement quickly get complicated to map out in your gets difficult extremely quickly tell where you have error, it's very, very easy a costly really an change you can just this: BEGIN; UPDATE reward_members SET = 'gold_group' WHERE member_status member_status = 'bronze_group' WHERE member_status = 'bronze'; UPDATE SET member_status = 'platinum_
point is that everyone I've talKed to from dEveloPerS to ThE CEO UndeRstand
that OpensTack Needs to be its own project. we (indIvIDualLY aNd as a Company)
ARe TRYinG tO sHepHeRD tHe proJecT.

------
jjdoe
"I Think that RAckSpAce is trying tO CoNtrol OpensTacK rather than iNflUence
iT."

SO thAT's why You'Re up iN arms oVEr them Making a moVe TO _reducE_ Their
prESEnCe on The board? Sure, they sHOuLD have handled it Better, BuT It SEEms
SilLy to jump frOm A bumbLIng move TO a POWEr gRAb, especially wHen the point
WAs tO reducE tHe nEAr-totaL domiNaTIon Of Rackspace On thE board aftEr the
ANSo purchASe.

WondeR if theRe aRe mOre sOUr GrApeS bEHinD ThIs tHAn yOu're lettInG oN.

------
lsc
iS anyONE REntiNg oUt inFrastRucture using tHe OPenSTAck aPI? SeEms to Me liKe
It'll bE more vAluabLe Both to consumers And tO providerS onCe TheRe Are
seVEral inTer-OpeRable prOviders. aLso, SoCIAL pRoof would make the
trAdITIoNally conServatIVe vPs ProviderS mOre ComfORTable, i thiNK.

 
MY FavoritE PostgRESqL queries AnD Why ThEy matTer - Grzm
hTTps://sEveralNines.com/Blog/mY-Favorite-postgrESql-queries-and-WHy-THEy-MAtteR
======
da_Chicken
> 6\. UPDAtE muLTiplE rowS WiTh a caSE exPressIoN

oh, MAn, as a seasoned DBA/DatA ANalyst, Don't dO this unless yoU have a
realLY GOod reasoN to. THIs IS premature optiMizatIon of the kiND you want To
avoId.

Yes, it's Really neaT TO update eVerYthIng In a SINgLe statement, anD IN
_somE_ sItuatioNs iT can perForM siGniFicAnTly better, But CASE eXpReSsIoNs iN
an UPdaTE stateMeNt qUiCklY get cOMplicaTed to Map oUt In YOur Head. It gETs
EXTremElY dIffiCulT eXtremEly qUIckLy to telL where you HavE An erRoR, aNd
it's veRy, very easy to mAkE a very costLy MisTake.

If YOU really nEed an atomic change you can JUst do thIs:

    
    
      BeGIN;
      UpDATe reward_meMbeRs SET mEmbER_statuS = 'gold_gRoup' WhErE mEMBer_stATUs = 'GolD';
      UpDATE rewarD_MEmbErs SEt mEmbeR_status = 'Bronze_group' WHERE meMBer_Status = 'bronze';
      UpDAtE reWARd_MemBErS sET MeMBer_STAtus = 'platinum_
point is that everyone I'v e talked t o fro m d eve lo pers  tothe CEO unders t andthat OpenStack needs t o beit s  own pr oject . We (i n di v i dua ll yand  a s  a  comp any )
are t rying to s hep he rd the proje c t. 

------
j jdo e
"I think t hat  Racks pa cei s try ing  to c ontrol Openst ack rathe rt han in f luencei t ." 

So  that's why you'r e  u p  in arms overthem m ak i ng a  mo veto _reduce _their presenc e  o n t heb oard? Sure, t hey shouldh ave  handl ed  it better , but  i t  se ems
silly t o ju mp from a  bumbl i ng move to a po wer gr ab,  es peci a ll ywhe nt hep oi ntw asto reduc eth e nea r-to t a l domi nat ionof Ra ckspace on th e b oard aft er th e
Ans o pu rc hase. 

Wond er if  t here are more s ourgrapes be hin dthi sthany ou'relet tin g on.
------l scis a n yo ne renting out inf ra s t ru cture us ing th e  O pe n Stack AP I?  Se emst o  me l ikei t' ll be mo re val u ab le  both t oconsum er s a ndto pr o vide rs onc e thereare
s e veral inter-op e rable provide r s. A ls o , so cia l proof wou ld m a ke t he
t r ad iti o nally  cons er v at i ve VPS providers mo re  comfo rtabl e, I think.
 
My Favor i t e  Postgre SQLQ ue r ies and Why Th ey Ma tter - grz m 
https:/ /seve ralnines .com/blog / m y-favori te- pos tgr esq l - qu eries-and-why - t hey- ma tter
== === =
da_ch ick en> 6 \.UP DATE mult iple row swi th  a  CA SE ex p ression
O h,ma n,as as easone d DBA /Dat aAn a lys t, don' t  d o this  u nl essyou  h ave a 
rea l lygood re ason to.Thi s  ispr em ature o ptimization o fthe kind y ou  wa nt toa v oid.

Ye s, it's really neat tou pdate e ver ythin g in  a single  st atemen t,a nd in_some_  situ at ion s it ca n pe rfo rm  significa n t lybette r,  but  CASE e xpressions in
an U P DAT E statement q uic klyg e tcom p li c ate dt o m a p  out in your he ad. It get se xt remely dif f icu lt  extrem ely qui cklyt o tellwhere you  have aner ror, a ndit's very,  very ea sy to mak e  a ve r ycostl y m istake .
If  youreally nee d anatomic  c hangeyou c an  just do  this:

    
    
     BEGIN ;
    UPDATE re war d _me mbers SET  mem ber_status  ='go ld_gr oup '  WHER E me m be r_s t atus= 'g o ld';
    U PDA T E  r eward_membe r s SET  memb er_ s tatus= 'b ronze_group' WHER E  member_status  = ' b r onz e';     UPDATE reward_ mem be r s  SET mem be r_status ='platinu m_ 
point is_that everyone_I've talked to from_developers to_the_CEO understand
that_OpenStack_needs to be_its own project._We (individually and as_a company)
are trying_to_shepherd the project.

------
jjdoe
"I think that Rackspace is trying to control Openstack rather than influence
it."

So_that's_why you're_up_in_arms over them making a_move to _reduce_ their
presence on_the board?_Sure, they should have handled it better, but_it_seems
silly to jump_from a bumbling move to a power grab, especially_when the point
was to reduce the_near-total domination of_Rackspace_on_the board after the
Anso_purchase.

Wonder if there are more sour_grapes behind this than you're letting_on.

------
lsc
is anyone renting out infrastructure using the_OpenStack API? Seems to me like
it'll_be more valuable both to_consumers and_to providers once there are
several_inter-operable providers. Also,_social proof_would make the
traditionally_conservative VPS providers more comfortable, I_think.

 
My Favorite_PostgreSQL Queries and Why They Matter_-_grzm
https://severalnines.com/blog/my-favorite-postgresql-queries-and-why-they-matter
======
da_chicken
> 6\. UPDATE_multiple_rows_with a_CASE expression

Oh, man,_as_a seasoned_DBA/Data_Analyst, don't do this unless you_have_a
really good reason to. This is premature_optimization of the kind_you_want to
avoid.

Yes, it's really_neat to update everything in_a single statement, and in
_some_ situations_it can_perform significantly_better, but CASE expressions in
an UPDATE statement quickly get complicated to_map out in your head. It_gets
extremely difficult extremely quickly_to tell_where_you have an_error,_and
it's very,_very easy to make a very costly_mistake.

If you_really need an atomic change you_can just do this:

__  
   _
     _BEGIN;
    __UPDATE_reward_members SET member_status = 'gold_group'_WHERE member_status = 'gold';
  _  _UPDATE reward_members SET member_status = 'bronze_group' WHERE_member_status_= 'bronze';
    __UPDATE reward_members SET member_status = 'platinum_