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

[Bug] Error creating new model #67

Closed
miquelangeld opened this issue Aug 29, 2023 · 7 comments
Closed

[Bug] Error creating new model #67

miquelangeld opened this issue Aug 29, 2023 · 7 comments
Assignees

Comments

@miquelangeld
Copy link

miquelangeld commented Aug 29, 2023

Hi Trying to create a new model (with crud and I get this error):

SQLSTATE[IMSSP]: An invalid attribute was designated on the PDO object. Exception

dev tools doesn't create any file, just throw the error. I'm able to generate the model (with crud, request, migration,etc.) using CLI and then migrate without any error.+

PHP VERSION:

PHP 8.1.22 (cli) (built: Aug 14 2023 05:32:33) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.22, Copyright (c) Zend Technologies
with Zend OPcache v8.1.22, Copyright (c), by Zend Technologies
with Xdebug v3.2.1, Copyright (c) 2002-2023, by Derick Rethans

LARAVEL VERSION:

10.20.0.0

BACKPACK PACKAGE VERSIONS:

backpack/backupmanager: v5.0.0
backpack/basset: 1.2.0
backpack/crud: 6.1.15
backpack/devtools: 2.0.3
backpack/editable-columns: 3.0.2
backpack/generators: v4.0.2
backpack/logmanager: v5.0.0
backpack/permissionmanager: 7.0.1
backpack/pro: 2.0.11
backpack/settings: 3.1.0
backpack/theme-coreuiv2: 1.1.4
backpack/theme-tabler: 1.0.12

Operating System and Server Setup

I'm using Laravel Sail on Ubuntu

@karandatwani92
Copy link

Hey @miquelangeld could you please share the stack trace?

@miquelangeld
Copy link
Author

there is a link in the first message https://flareapp.io/share/NPL8k9XP

@karandatwani92
Copy link

So, you created a very basic model(id, name, timestamp).
I did the same with devtool. it worked.

is there anything else I'm missing to reproduce the error?

@miquelangeld
Copy link
Author

I think it's a problem with certain PHP versions. Today I had the same error in my project using the MSSQL driver which never happened before. I founded this thread laravel/framework#47937 and maybe it's a problem with some PHP versions. I'm doing some tests in order to check it.

@pxpm
Copy link

pxpm commented Sep 6, 2023

Sorry @miquelangeld MSSQL is not officially supported. 😞

We are aware of some issue with that platform #64

Can you try that fix and let us know if it worked for you ?

Cheers

@miquelangeld
Copy link
Author

miquelangeld commented Sep 7, 2023

Hi @pxpm Maybe I haven't explained myself. The issue that I created here is not related with MSSQL my laravel project uses mysql as main database engine.

I just posted as additional context that I realized that I suddenly had the same error interacting also with MSSQL at the same time that devtools started to fail (In my project I get some info from several external DBs)

And this circumstance makes me think that the problem lies elsewhere and not in the devtools.

I have found that in some minor versions of PHP devtools gives the mentioned error. With 8.1.22 it fails, but with 8.1.17 it doesn't. (I have two projects with laravel sail with different php versions and I have been able to test it).

Take a look here laravel/framework#47937 It seems that some minor versions of PHP have problems when using certain database drivers, maybe it also happens with sqlite (I think that's de DB used by devtools).

I have managed to get those versions of PHP and the MSSQL driver working by adding these options to the configuration.

'options' => [
                PDO::ATTR_ERRMODE => PDO::ERRMODE_SILENT,
            ]

But in the case of devtools I have not been able to get it to work. But I'm pretty sure that it's a PHP problem, so maybe we should close the issue. If I find out how to solve the problem with this php versions I will comment here anyway.

I hope I have explained myself better ;)

@pxpm
Copy link

pxpm commented Sep 7, 2023

Yes, indeed you explained yourself very well. Thanks for the clarification 🙏

I will be closing this for now then, if you find the concrete problem, and is something we can fix on our side, let us know.

Cheers

@pxpm pxpm closed this as completed Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

3 participants