Raphael Guzman

@jverswijver From our prior discussion, the largest issue I see here is that if we are properly addition `loglevel` to be used in the config, we should verify the case...

Thanks for your interest @MadhuMPandurangi! We always appreciate any help you can provide. :smiley: We welcome all PR's but I might suggest having a look at these [good-first-issues](https://github.com/datajoint/datajoint-python/issues?q=is%3Aopen+is%3Aissue+label%3Agood-first-issue). We've recently...

@chrisroat Thanks for the PR and good stuff here man! :rocket: We are currently playing a bit of some catch-up on other regression issues and new team members (they've recently...

Read-only users also discussed in #636

Related https://github.com/datajoint/datajoint-python/issues/687

From separate Slack discussions, a possible syntax was presented as: `section = dj.Diagram(schema) & (Session & 'subject=1')`

Met with @ttngu207 (thanks man!) for a debug session and was able to identify the root cause and successfully reproduce the issue on my side. Should be a simple fix...

@a-darcher Thank you for the report but I'm afraid there may be bit of confusion here. :sweat_smile: In DataJoint Python, you must connect to a MySQL-compatible database server to store...

Thanks for your interest @MadhuMPandurangi! We always appreciate any help you can provide. :smiley: We welcome all PR's but I might suggest having a look at these [good-first-issues](https://github.com/datajoint/datajoint-python/issues?q=is%3Aopen+is%3Aissue+label%3Agood-first-issue). We've recently...

@CBroz1 Thanks for the feedback. In reviewing the ask and the snippet you shared, I'd recommend having your `drop_schemas` feature actually iterate through the tables in the diagram instead; bottom...