[BioMart Users] Any way to not display NULL columns?

[Prateek Kumar]

Hi

I am trying to use the single merged table approach for handling multiple-subtype attributes. This means for a given query there will be some attributes that will always have NULL value. Is there any way to avoid displaying NULL columns?

Thanks

Prateek

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users

[Syed Haider-2]

Prateek,

Would hiding such attributes from the web interface (effectively from
API access too) not suffice ? Or you are looking for an automated
solution whereby all such columns are hidden by default, which is indeed
not possible at this stage.

Best,
Syed


On 29/05/2012 19:22, Prateek Kumar wrote:

> Hi
>
> I am trying to use the single merged table approach for handling
> multiple-subtype attributes. This means for a given query there will be
> some attributes that will always have NULL value. Is there any way to
> avoid displaying NULL columns?
>
> Thanks
> Prateek
>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> https://lists.biomart.org/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users

[Arek Kasprzyk]

hmm ... this should be a default software behaviour just like in 07. If this is not working in 08 rc6, then this is a bug that needs to be fixed

a

On Tue, May 29, 2012 at 1:22 PM, Prateek Kumar <[hidden email]> wrote:

Hi

I am trying to use the single merged table approach for handling multiple-subtype attributes. This means for a given query there will be some attributes that will always have NULL value. Is there any way to avoid displaying NULL columns?

Thanks

Prateek

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users

[Prateek Kumar]

Arek, Syed

Thanks for your response. 

I am ok with the attributes being visible in the form but I was looking for a way to hide them from the returned results where biomart currently reports NULL values as "no data". Can 07 hide columns with all returned cells having "no data"?

Thanks

Prateek

On Thu, May 31, 2012 at 8:36 AM, Arek Kasprzyk <[hidden email]> wrote:

hmm ... this should be a default software behaviour just like in 07. If this is not working in 08 rc6, then this is a bug that needs to be fixed

a

On Tue, May 29, 2012 at 1:22 PM, Prateek Kumar <[hidden email]> wrote:

Hi

I am trying to use the single merged table approach for handling multiple-subtype attributes. This means for a given query there will be some attributes that will always have NULL value. Is there any way to avoid displaying NULL columns?

Thanks

Prateek

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users

[Arek Kasprzyk]

Hi Prateek,

I don't think so. As far as I know the only mechanism to get rid off the NULL columns is not to display the corresponding attributes

a

On Fri, Jun 1, 2012 at 4:23 PM, Prateek Kumar <[hidden email]> wrote:

Arek, Syed

Thanks for your response. 

I am ok with the attributes being visible in the form but I was looking for a way to hide them from the returned results where biomart currently reports NULL values as "no data". Can 07 hide columns with all returned cells having "no data"?

Thanks

Prateek

On Thu, May 31, 2012 at 8:36 AM, Arek Kasprzyk <[hidden email]> wrote:

hmm ... this should be a default software behaviour just like in 07. If this is not working in 08 rc6, then this is a bug that needs to be fixed

a

On Tue, May 29, 2012 at 1:22 PM, Prateek Kumar <[hidden email]> wrote:

Hi

I am trying to use the single merged table approach for handling multiple-subtype attributes. This means for a given query there will be some attributes that will always have NULL value. Is there any way to avoid displaying NULL columns?

Thanks

Prateek

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
https://lists.biomart.org/mailman/listinfo/users