Suggestion: "Active" column in platforms

[Erik Eloff]

Hello!

Sorry I've been away for too long...

I have a suggestion on the database schema that I'd like to discuss.
The platforms table needs a "active (bool)" column. Just as in builds,
testplans, testprojects etc..

Active should be default to true.
Active = false means this platform can no longer be assigned to a
testplan. Links and assignments that are already made should still be
working.

Thoughts?

Regards,
Eloff

[Martin Havlat]

I'm fine with this field.
Martin

> --
>
> You received this message because you are subscribed to the Google Groups "testlink-dev" group.
> To post to this group, send email to testli...@googlegroups.com.
> To unsubscribe from this group, send email to testlink-dev...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/testlink-dev?hl=en.
>
>
>
>


--
This message was scanned by ESVA and is believed to be clean.

[Francisco Mancardi]

Erik Eloff wrote:
> Hello!
>
> Sorry I've been away for too long...
>
> I have a suggestion on the database schema that I'd like to discuss.
> The platforms table needs a "active (bool)" column. Just as in builds,
>

Firts BOOL type is not standard for tl => CAN NOT BE USED

> testplans, testprojects etc..
>
> Active should be default to true.
> Active = false means this platform can no longer be assigned to a
> testplan. Links and assignments that are already made should still be
> working.
>
> Thoughts?
>

Need more details => consider what will happen with EVERY TL FEATURE
were platforms are used.
What will happen with test cases assigned with this platform ?
What will be happen on test case assignment feature ?

With the detail of analisis provided in this mail, development can not
start because side effects are not clear =>
my vot is reject till a detailed analisys will not be provided.

Anyway this feature can not be on 1.9.

[Martin Havlat]

See inline.
Regards,
Martin

Francisco Mancardi wrote:

Erik Eloff wrote:
  

Hello!

Sorry I've been away for too long...

I have a suggestion on the database schema that I'd like to discuss.
The platforms table needs a "active (bool)" column. Just as in builds,
  
    

Firts BOOL type is not standard for tl => CAN NOT BE USED
  

@Francisco, did I understand it correctly, that you means database type?
  `active` tinyint(1) NOT NULL default '1',
Indeed boolean is real behaviour.

testplans, testprojects etc..

Active should be default to true.
Active = false means this platform can no longer be assigned to a
testplan. Links and assignments that are already made should still be
working.

Thoughts?
  
    

Need more details => consider what will happen with EVERY TL FEATURE 
were platforms are used.
What will happen with test cases assigned with this platform ?
What will be happen on test case assignment feature ?

With the detail of analisis provided in this mail, development can not 
start because side effects are not clear =>
my vot is reject till a detailed analisys will not be provided.

Anyway this feature can not be on 1.9.
  

Are you fine to implement this feature within 2.0 version or was your expectation different?

[Francisco Mancardi]

Martin Havlat wrote:

See inline.
Regards,
Martin

Francisco Mancardi wrote:

Erik Eloff wrote:
  

Hello!

Sorry I've been away for too long...

I have a suggestion on the database schema that I'd like to discuss.
The platforms table needs a "active (bool)" column. Just as in builds,
  
    

Firts BOOL type is not standard for tl => CAN NOT BE USED
  

@Francisco, did I understand it correctly, that you means database type?
  `active` tinyint(1) NOT NULL default '1',
Indeed boolean is real behaviour.

Yes, but ONLY TYPE supported by Postgres,MySQL, MSSQK must be used

testplans, testprojects etc..

Active should be default to true.
Active = false means this platform can no longer be assigned to a
testplan. Links and assignments that are already made should still be
working.

Thoughts?
  
    

Need more details => consider what will happen with EVERY TL FEATURE 
were platforms are used.
What will happen with test cases assigned with this platform ?
What will be happen on test case assignment feature ?

With the detail of analisis provided in this mail, development can not 
start because side effects are not clear =>
my vot is reject till a detailed analisys will not be provided.

Anyway this feature can not be on 1.9.
  

Are you fine to implement this feature within 2.0 version or was your expectation different?

With not enough time this feature MUST BE 2.0 and not before, IMHO

[Daiane Casagrande Patrício Broca]

Olá, Alguém do grupo fala português?

--
att,

Daiane Casagrande Patrício Broca
daia...@gmail.com

Twitter: http://twitter.com/daianecpb
Blog: http://daianecpb.blogspot.com
Skype: daia...@gmail.com

[Francisco Mancardi]

Daiane Casagrande Patrício Broca wrote:

Olá, Alguém do grupo fala português?

very bad practice to use a subject to ask for other thing, please avoid it

--
att,

Daiane Casagrande Patrício Broca
daia...@gmail.com

Twitter: http://twitter.com/daianecpb
Blog: http://daianecpb.blogspot.com
Skype: daia...@gmail.com

--