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

Laravel postgresql set charset broken #19107

Closed
lastonoga opened this issue Oct 7, 2017 · 3 comments
Closed

Laravel postgresql set charset broken #19107

lastonoga opened this issue Oct 7, 2017 · 3 comments
Assignees
Labels
O-community Originated from the community

Comments

@lastonoga
Copy link

When i use postgresql driver, migrating shows errors like

[Illuminate\Database\QueryException]                                                                                
  SQLSTATE[XX000]: Internal error: 7 ERROR:  unimplemented at or near "utf8"                                          
  set names 'utf8'                                                                                                    
            ^ (SQL: select * from information_schema.tables where table_schema = public and table_name = migrations)  

I found some threads there. Seems like bug is fixed.
I tried to change charset property to null, but anyway it doesn't fix situation.

Config

'pgsql' => [
            'driver' => 'pgsql',
            'host' => env('DB_HOST', 'localhost'),
            'port' => env('DB_PORT', '5432'),
            'database' => env('DB_DATABASE', 'forge'),
            'username' => env('DB_USERNAME', 'forge'),
            'password' => env('DB_PASSWORD', ''),
            'charset' => null,
            'prefix' => '',
            'schema' => 'public',
        ],

Error

Internal error: 7 ERROR:  unimplemented at or near ""                                              
  set names ''               
@maddyblue
Copy link
Contributor

Thanks for this report. We don't yet support set names. Assigning for triage.

@dianasaur323 dianasaur323 added the O-community Originated from the community label Oct 10, 2017
@justinj
Copy link
Contributor

justinj commented Oct 11, 2017

We actually do support SET NAMES as of #16305, this should work in 1.1.

@maddyblue
Copy link
Contributor

Closing this issue then. Please comment or reopen if we closed incorrectly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-community Originated from the community
Projects
None yet
Development

No branches or pull requests

5 participants