;

I get an error in the third line.
If I leave the query like this, without specifying the data type for Column2, the query works, but the default data type will be int, whereas I want to have VARCHAR. 
CREATE VIEW VIEW2
AS SELECT [Column1],
(NULL) AS column2 
FROM VIEW1;

Can you please help? Thank you!
Note: Only Column1 is in VIEW1. Column2 is NOT in VIEW1, it's a generated column with NULL values. 

A:

You'll want this.
CREATE VIEW VIEW2
AS SELECT [Column1],
cast(NULL as varchar(10)) AS column2
FROM VIEW1;

 Q:

Sense of unit tests without TDD

We have new (quite big) project starting, that we planned to develop using TDD.
The idea of TDD failed (many business and non-business reasons), but right now we have a conversation - should we write unit tests anyway, or not. 
My friend says that there is no (or close to zero) sense in writing unit tests without TDD, we should focus only on integration tests. I believe the opposite, that there is still some sense in writing plain unit tests, just to make code more futureproof. What do you think?
Added:
I think that this is not a duplicate of >>this question<< - I understand difference between UT and TDD. My question is not about differences, but about sense of writing Unit Tests without TDD.

A:

TDD is used mainly (1) to ensure coverage, (2) and to drive maintainable, understandable, testable design. If you don't use TDD, you don't get guaranteed code coverage. But that in no way means that you should abandon that goal and blithely live on with 0% coverage. 
Regression tests were invented for a reason. The reason is that in the long run, they save you more time in prevented errors than they take in additional effort to write. This has been proven over and over again. Therefore, unless you are seriously convinced that your organization is much, much better at software engineering than all the gurus who recommend regression testing (or if you plan on going down very soon so that there is no long run for you), yes, you should absolutely have unit tests, for
; 

 I get an error in the third line. 
 If I leave the question like this, without specify the data type for Column2, the question works, but the default option data type will be int, whereas I want to hold VARCHAR. 
 CREATE VIEW VIEW2 
 AS SELECT [ Column1 ], 
 (NULL) AS column2 
 FROM VIEW1; 

 Can you please help? Thank you! 
 notice: merely Column1 is in VIEW1. Column2 is NOT in VIEW1, it's a generated column with NULL values. 

 adenine: 

 You'll want this. 
 CREATE VIEW VIEW2 
 AS SELECT [ Column1 ], 
 cast(NULL as varchar(10) ) AS column2 
 FROM VIEW1; 

  Q: 

 common sense of unit tests without TDD 

 We have new (quite big) project starting, that we plan to develop using TDD. 
 The idea of TDD fail (many business and non - business reasons), but right now we experience a conversation - should we write unit tests anyway, or not. 
 My friend allege that there is no (or close to zero) sense in writing unit test without TDD, we should concenter only on integration tests. I believe the opposite, that there is still some sense in spell plain unit examination, barely to make code more futureproof. What do you think? 
 Added: 
 I think that this is not a duplicate of > > this question < < - I understand remainder between UT and TDD. My question is not about differences, but about sense of writing Unit Tests without TDD. 

 A: 

 TDD is used mainly (1) to see coverage, (2) and to drive maintainable, understandable, testable design. If you don't use TDD, you don't catch guaranteed code coverage. But that in no manner means that you should abandon that goal and blithely live on with 0% coverage. 
 arrested development tests were invented for a reason. The reason is that in the long run, they save you more time in prevented error than they take in extra effort to write. This has been proven over and over again. consequently, unless you are seriously convinced that your organization is much, much better at software technology than all the gurus who recommend regression examination (or if you plan on going down very soon so that there is no long run for you), yes, you should absolutely have unit tests, for
;

I gft an error in the third line.
If I leave the quxry liks this, wkthout specifying the data tbpe dor Cilumn2, the query works, cut the dvfault dara tbpe will be int, xgereas L wanf to kate VARCHAR. 
CREAJE VIEW VIEW2
DS SELECT [Colukn1],
(VUPL) AS column2 
FROM VIEW1;

Can you pleasq help? Yhwnk you!
Note: Onjy Cpjumn1 ps in VIEW1. Column2 is NOT in VIES1, it's a generated cokumn with NULL values. 

A:

You'pl wwnt this.
CREATE VIEA VIEW2
AS SEOECT [Xolumn1],
cast(NUUL as varchar(10)) AS columh2
FROM VIEW1;

 Q:

Sense of unit tests withput TDD

We yace jgw (quite big) projvct starting, bnat we plannec to develop uxinj TDE.
The idea of TDD failxd (many business and non-businasa reasons), but rigyt now fe hdve x covvedsetikn - shlulv we write hnit tests qnyway, or not. 
My froege says that tgere if go (or close to zero) sense in writing unpt tssts without TDD, we shoyld focus only on intggration tqsts. I believe the opposite, that there is still smme sxnre nk deihing plain unit tests, just to make code more shtirvproof. What do yom think?
Added:
I thinl hhsj this is not x duplndafe of >>this questioj<< - I unqerstqnd diffewencr between UT and TDD. My quewtion is not qbout differences, yut about seuse of writong Unit Tests without CDD.

A:

TDS is used mwinly (1) to dnsure coverage, (2) anc do drive maintainable, undewstandablx, tescable derign. If yot don't use TDD, nmu don't get guaranheed eode woverage. Bkt that in no way means that yon should abancot tvat goal and nlithely live og with 0% coveraye. 
Regrefsion tests werv inventev for a reasjn. The reason ls that in tie long rtn, tyey wave yoj more time in lrevented errors thqn they take in advitiuhal effort to wxntt. Rhis has been lroxen oner agg over again. Thefefute, unuess you arc sdrioisly convinced that four organization is micm, much bejter at sjftware enginrering than all tht guruv wio recpmmgnd regression testing (or if yoh plan on golng down very sook so that therz is no long run for you), yes, you should ebsolutely have unit tgsts, for
; I get an error in the If leave the like this, without Column2, query works, but default data type be int, whereas I want to VARCHAR. CREATE VIEW VIEW2 AS SELECT [Column1], (NULL) AS column2 FROM VIEW1; Can please help? Thank you! Note: Only Column1 is in VIEW1. Column2 is NOT VIEW1, a column NULL values. A: You'll want this. CREATE VIEW VIEW2 AS SELECT [Column1], cast(NULL as varchar(10)) AS FROM VIEW1; Q: Sense of unit tests without We have new (quite project starting, that we planned develop TDD. The of failed business and non-business but right now we have a conversation - should we write unit tests anyway, or not. My says that no (or to sense writing unit tests we should focus only on integration the opposite, that there is still some sense writing plain tests, just to make code more What do you think? Added: I think that is not a duplicate of >>this question<< - I understand difference between UT and TDD. is not about differences, about sense of Unit without A: is used (1) to ensure coverage, (2) and to drive maintainable, understandable, testable If you don't use TDD, you don't get guaranteed code that no way means you should abandon that and live on with 0% tests invented The is in the long run, save you more time in errors than they take This has been proven over and over again. unless you are seriously convinced that your is much, much better at software engineering than all the gurus who regression testing you plan on going down very soon so there is no long for you), yes, you should absolutely have unit tests,
;

I get an error in the third line.
if I leave thE querY liKe tHiS, witHout Specifying the dATa tyPe for Column2, the query worKs, but ThE DefaULt Data tYpe will BE iNT, WheReAs i waNt TO hAve VArCHaR. 
CREATe VIEW VIEW2
As SElEcT [Column1],
(NULL) as cOlumn2 
FROM ViEW1;

can you please HelP? Thank YoU!
NoTE: Only colUmn1 is In VIEW1. cOlumn2 iS NOT in VIEw1, iT'S a geneRAted colUMN wIth NuLL values. 

A:

You'll waNT tHIs.
CREATE VIEW VIeW2
AS SElEct [COLUmn1],
CasT(NULL as varChAr(10)) AS cOLumn2
FROm vIew1;

 q:

senSE of unit tests wIthout TDD

We HAve New (quiTe Big) PRoject StartInG, ThaT we planned tO devElop using tDD.
The IDea of TDd Failed (mAny busIneSs aNd noN-BuSiNesS rEAsoNS), bUt rIGht Now we havE a CoNversAtioN - SHOUld wE wrIte uNit teSts anyway, or noT. 
My FrieND saYs thaT therE is nO (oR closE to zerO) sensE iN writing unit tesTs wiThout TDD, wE shOuLd fOcUs onlY On inteGraTioN tests. I Believe THe oPpOSITe, That there is still soMe SENsE in writiNg plaiN UnIt TEsts, just To MakE codE MOre fuTurePRoOf. What do You thiNK?
ADdEd:
I thinK tHat thiS iS noT a dUplicATe of >>This quEstion<< - I uNdersTAnd difference bETween UT and TDD. mY qUEStIOn is Not About differEnceS, But aBout SEnSe oF WritiNg UniT TEStS Without TDD.

A:

TDD is useD mAinly (1) tO ensuRe coverage, (2) and To drive maiNTAInable, unDersTAnDAble, testable deSign. IF you don't usE tDD, you doN't get GuaranteEd code covERAge. But thAt iN no Way MeaNS ThAt you should abANDon tHaT goal anD blIthely lIve On wIth 0% CovErAge. 
RegresSion testS wErE iNvEntEd for A Reason. ThE rEasOn Is tHat in THe long Run, thEy saVe YoU MorE time in PReVENted ErRoRs thAn tHeY take In adDItiOnal effOrt to writE. ThIS has BeEn Proven oVer and over agaIn. therefore, uNlEss You are SERiously cOnvinced that your organizATion is mUch, Much bEtteR at softwaRe eNgineeRinG Than alL the guRus whO rEcoMMEnd reGREsSioN tEsting (or if YOU plAn on gOiNg doWn very sOon so that there is no LOng Run for you), yes, yOu sHoulD ABsOluTElY HavE uNIt tESTs, for
;

I get an error in the t hird line. 
If I  le ave  t he q uery  like this, wi t hout  specifying the data t ype f or Colu m n2 , the  queryw or k s , b ut  t hede f au lt da tatype wi ll be int,  wh er eas I want t o  h ave VARCHA R.
CREATE VIEW  VI EW2
AS  S ELE C T [Co lum n1],(NULL) AS col umn2 
FRO MV IEW1;Can you p le asehelp? Thank you!N ot e : Only Column1  is in  V I EW 1 .  Co lum n2 is NOTin  VIEW 1 , it'sa  g e n e rat e d column with  NULL value s . 
A:

Y ou 'll want t his.CR E ATE  VIEW VIEW2 
ASSELECT [C olumn1 ] ,
cast( N ULL asvarcha r(1 0))  ASc ol um n2FR O M V I EW 1; Q: 

Senseof  u nit t ests w i t hout  TD D

W e hav e new (quitebig ) pr o jec t sta rting , th at  we p lanned  to d ev elop using TDD. 
The  idea ofTDD  f ail ed  (man y  busin ess  an d non-b usiness rea so n s ) ,but right now we h av e aconversa tion - sh ou l d we wri te  un it t e s ts an yway ,  o r not. My fri e nd  s ays tha tthereis  no  (o r clo s e to  zero)  sense i n wri t ing unit tests without TDD,w es h ou l d fo cus  only on in tegr a tion  tes t s.  Ib eliev e the  o p po s ite, that there isst ill so me se nse in writin g plain un i t tests, j ustt om ake code morefutur eproof. Wh a t do you  thin k?
Added :
I think t hat this  is  no t a  du p l ic ate of >>this q uest io n<< - I  un derstan d d iff ere nce  b etween UT  and TDD .My  q ue sti on is not abou tdif fe ren ces,b ut abo ut se nseof  w r iti ng Unit Te s t s wi th ou t TD D.
A :

TD D is use d mainl y (1) toens u re c ov er age, (2 ) and to driv emaintainab le , u nderst a n dable, t estable design. If youd on't us e T DD, y ou d on't getgua rantee d c o de cov erage.  Butth ati n  no w a y  m ean sthat you s h o uld  aban do n th at goal  and blithely live onwith 0% cover age . 
R e g re ssi o nt est sw ere i nvented for a r eason. The  r e as on is that inth e longrun, th ey sa v e you m ore timein preven te d er r o rsthan theytake inadditiona l  effo r tto wr ite . This  h asbeenproven ove r and  overag ain. T heref or e, unles s you are seriously con vinced  that  yo ur organi zat i onis much,much  better at  so ftw are e ngi n eerin g th a nall the g urus who recom m en d r e g re ssion testi n g (or  if y oup lan on  goi ng down very soon so that thereis n o lon g r u n fo ryou), yes, you  sh ou l d  absolut el y have unit  tests,fo r 
;

I get_an error_in the third line.
If_I leave_the_query like_this,_without specifying the_data type for_Column2, the query works,_but the default_data_type will be int, whereas I want to have VARCHAR. 
CREATE VIEW VIEW2
AS SELECT_[Column1],
(NULL)_AS column2_
FROM_VIEW1;

Can_you please help? Thank you!
Note:_Only Column1 is in VIEW1._Column2 is_NOT in VIEW1, it's a generated column with_NULL_values. 

A:

You'll want_this.
CREATE VIEW VIEW2
AS SELECT [Column1],
cast(NULL as varchar(10)) AS column2
FROM_VIEW1;

 Q:

Sense of unit tests without_TDD

We have new_(quite_big)_project starting, that we_planned to develop using TDD.
The idea_of TDD failed (many business and_non-business reasons), but right now we have_a conversation - should we write_unit tests anyway, or not._
My friend_says that there is no_(or close to_zero) sense_in writing unit_tests without TDD, we should focus_only on integration_tests. I believe the opposite, that_there_is still some_sense_in_writing plain_unit tests, just_to_make code_more_futureproof. What do you think?
Added:
I think_that_this is not a duplicate of >>this_question<< - I understand_difference_between UT and TDD._My question is not about_differences, but about sense of writing_Unit Tests_without TDD.

A:

TDD_is used mainly (1) to ensure coverage, (2) and to drive_maintainable, understandable, testable design. If you_don't use TDD, you_don't get_guaranteed_code coverage. But_that_in no_way means that you should abandon that_goal and_blithely live on with 0% coverage._
Regression tests were invented_for_a reason. The reason is that_in the long run, they save_you more time in prevented_errors_than_they take in additional effort_to write. This has been proven_over and over_again. Therefore, unless you are seriously convinced_that_your organization is much, much better_at_software engineering than all the gurus_who_recommend_regression testing (or if you_plan on going down very soon_so that there is no long run for you),_yes, you should_absolutely have unit tests, for