Return Type of resource replace by class

[jansor]

Hi,

I was wondering, as I understand the type of resource is something in the future version they going to deprecate/replace.
Now when i was just playing around with CURL under PHP8.0 and saw following items in documentation.

The documentation is based for PHP Storm, but is their a similar implementation possible?

As an example that's direct from PHP: https://www.php.net/manual/en/class.curlhandle.php

As a future implementation towards 8.1 or next version, can we apply the same logic under the SQL system?

Just a suggestion

Thanks for all the hard work!!

[yitam]

Thanks @jansor , and yes we are aware of the resource type going to be deprecated in the near future, but I'm not sure I understand your question.

Are you asking if we are going to define our own class(es) for sqlsrv/pdo_sqlsrv to communicate with SQL Server?

[jansor]

Hi @yitam , i assume yes,

I don't know how to implement this but for future releases of the driver, add opaque class? Similar to CurlHandle?

final SqlSrvHandle{ }

Under the documentation part its then possible to add:

This gives the advantage that we can define return types on methods and properties.

[yitam]

Thanks @jansor for the suggestion. Currently there is no immediate plan for this, but I'll mark this as a feature request.

[codemasher]

I was just looking for this - it would be great to see in a future release! The PostgreSQL drivers also return an instance of a class rather than a resource as of PHP 8.1 (https://www.php.net/manual/en/class.pgsql-connection.php).
It allows for more type safety as one could check with an instanceof instead of the weird gettype() and looking for a resource type name.

[jansor]

With all the new development going on I hope this also gets a P1 or P2 tag ;)
btw thanks for the new releases and development, they are very welcome!!!

[jahnvi480]

@jansor Thank you for the kind words, it’s really great to see this level of excitement from the community around the ongoing development of msphpsql! 🚀

We’re just as excited about the progress we’re making, and feedback like this truly motivates us as we continue to improve the driver experience for our users.

We’ve taken note of this request and will be prioritising this GitHub issue in our upcoming planning discussions. Stay tuned for updates in future releases!