Change PDO::PARAM_NULL to resolve to SQLT_CHR #6
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When inserting NULLs for columns on & off in the definition below the value entered was a string of "0"
```php
schema::create('on_off_messages', function (Blueprint $table) {
$table->increments('id', 'device_status_bits_pk');
$table->string('on', 64)->nullable();
$table->string('off', 64)->nullable();
});
```
This change allows NULLs to be entered. It appears that NULLs are still entered into integer fields correctly too, though I would advise this is tested in your environment too!
yajra
added a commit
that referenced
this pull request
Jun 19, 2014
Change PDO::PARAM_NULL to resolve to SQLT_CHR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When inserting NULLs for columns on & off in the definition below the value entered was a string of "0"
This change allows NULLs to be entered. It appears that NULLs are still entered into integer fields correctly too, though I would advise this is tested in your environment too!