You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So going by baby steps that task above basically means that this works
CREATE FUNCTION overpaid ()
RETURNS boolean
AS $$
from ortools.linear_solver import pywraplp
return False
$$ LANGUAGE plpython3u;
Where "figure out how to import a module " means that
from ortools.linear_solver import pywraplp
is not how you import that module that is needed on a postgres function, because it fails.
Do baby steps mean that you keep your focus on the task at hand, which is to import the module that is needed, do not add more code that gets on the way for the task at hand.
If you comment out that
# from ortools.linear_solver import pywraplp
the tests will run smoothly I think.
I am going to do that.
hmm, I am maybe doing more changes.
In my computer it is running.
but on the action I am getting:
psql:setup_db.sql:17: ERROR: could not open extension control file "/usr/share/postgresql/14/extension/plpython3u.control": No such file or directory
Fixing the actions, don't know how many tries I will make
I will not fix my licence aaction, but you, please make sure to have the license on your sql files
file with all the working examples of the python documentation of postgresql
file with the python example of or_tools https://developers.google.com/optimization/introduction/python
figure out how to send a notice/warning/exception message
creating a type
figure out if without creating a type there can be output
continue growing the example
find more examples
The text was updated successfully, but these errors were encountered: