excute(update_query) return influenced rows about building-data-science-applications-with-fastapi HOT 6 CLOSED

Hi @66dexmg 👋

Do you get a specific error when doing this?

from building-data-science-applications-with-fastapi.

@frankie567
Yes,it may be a small mistake.In next row,i can only get first post which was not the post i updated because the function 'execute' always return the number 1.

from building-data-science-applications-with-fastapi.

You're perfectly right @66dexmg, that's actually quite a dumb mistake from my part. You can find the correct, fixed code here: e95e35f

I'll now contact Packt to coordinate a proper erratum. Thank you for raising this 🙏

from building-data-science-applications-with-fastapi.

@frankie567
You are welcome.You have written a fantastic book although I had waitted its Chinese translation for a long time😀.Any oriented advice for me after I finish it?

from building-data-science-applications-with-fastapi.

Thanks!

Well, my main advice to fellow developers is usually: practice. It's by experimenting a lot, building new things, observe what others are doing in their code that you'll make progress and gain experience.

That said, there are a few subjects I didn't have the opportunity to show in the book that are interesting:

• Worker process: when you have long-running operations to perform, it's usually a good idea to offload it to a background process, different from your web server. This way, you keep your API fast and responsive while being able to perform large jobs (data extraction, heavy machine learning...) in the background. In Python, this can be achieved with Celery or Dramatiq.
  • I have a quick introduction to those concepts in this blog post: https://www.francoisvoron.com/blog/create-deploy-reliable-data-ingestion-service-fastapi-sqlmodel-dramatiq
• Structured logging: for robust production systems, it's important to have clear logs to monitor what's going on. An interesting pattern is to structure those logs using JSON objects rather than just free-text logs. It'll help you search through them or index them correctly into a log ingestion platform like Logstash. Libraries to help you with this: structlog or loguru.
• Monitoring: it can also be valuable to have relevant metrics about your system (speed, number of operations...). A good approach is to set-up Prometheus, which is a lightweight but powerful way to define and report metrics. It's quite simple to add it in your Python codebase and then be able to properly query and display this data in a Grafana dashboard.

from building-data-science-applications-with-fastapi.

Thanks a lot!

from building-data-science-applications-with-fastapi.