graphql-python / graphql-python/graphene-sqlalchemy
Deferred columns inconsistency
- Linguagem predominante
- Python
- Estrelas
- 985
- Forks
- 223
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Descrição
We are using deferred column:
```
d_column = column_property(
func.pg_func(id), deferred=True)
```
It gave a naming error -- as SQL Alchemy generated column name on that. Hence we label it:
```
d_column = column_property(
func.pg_func(id).label('test'), deferred=True)
```
All works fine since that point, but this column doesn't appear in a sort.
Questions:
* Should it appear?
* If not -- why its name is validated?
Guia de contribuição
Direção de pesquisa
Start by reproducing the deferred column_property example with SQLAlchemy and inspect the repository's sorting and column-name validation entry points; no file or test is named in the issue. Compare labeled and unlabeled deferred columns, then establish and test the intended behavior for sorting and validation.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- graphql, python, sqlalchemy
- Domínio
- api, databases
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100