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.

Sign up for GitHub

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

Jump to bottom

fix nullable field #113

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

fix nullable field #113

wants to merge 1 commit into from
+1 −1

Conversation

evstratbg
Copy link

db_string doesn't use \N, only null

@evstratbg
fix fields
baca881 
db_string doesn't use \\N, only null
@r-bit-rry
Copy link
Contributor

r-bit-rry commented Jun 24, 2019 •
edited
Loading

@evstratbg Thanks for opening the PR
The ORM works with TabSeparated format when performing SELECT/INSERT queries, and when using tab separated format the output value for null from the DB is '\N'. This can easily be shown using the clickhouse-client:

FORMAT TabSeparated

\N

1 rows in set. Elapsed: 0.003 sec```
Can you please provide an example where the usage of \N caused a problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@evstratbg @r-bit-rry