Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No results and no error in query select with 21 columns or more #65

Closed
ajoses opened this issue Jul 20, 2018 · 4 comments
Closed

No results and no error in query select with 21 columns or more #65

ajoses opened this issue Jul 20, 2018 · 4 comments

Comments

@ajoses
Copy link
Contributor

ajoses commented Jul 20, 2018

Hi,

Whe you have a query with two tables and in the select you put specific columns of both tables, the Query function return no result, if I use and select * from both tables then it works.

I attach a program and a example database where I reproduce this error.

All the querys of the file where tested with flamerobin and run correctly, however I don't know why in the go program doesn't work.

Any comment to where I can look for the error will be appreciated.

PRUEBAS.zip
main.zip

@ajoses
Copy link
Contributor Author

ajoses commented Jul 20, 2018

My version of go:
go version go1.10.3 linux/amd64

Firebird:
LI-V2.5.7.27050 Firebird 2.5

@ajoses
Copy link
Contributor Author

ajoses commented Jul 20, 2018

Hi,
I ran some more tests, and found that the error is the number of columns selected, if there are more than 21 then it not return the value even thought the query has results.

I attached another serie of tests where I tested with one relation and with two relation.

I tried to find the code with the problem, but with no success.

Any orientation will be appreciated.
main.zip

@ajoses ajoses changed the title No results in select with columns of different tables No results and no error in query select with 21 columns or more Jul 21, 2018
@nakagami
Copy link
Owner

thanks
i will check it later

nakagami added a commit that referenced this issue Jul 22, 2018
Possible solution to issue #65
@nakagami
Copy link
Owner

Thanks
merge pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants