-
Notifications
You must be signed in to change notification settings - Fork 169
Purge open Issues and Pull Requests #74
Comments
Ping ? |
Sorry, I'm kinda lazy guy... I'm not the project owner so I have no access to pypi. And sometimes I need some time to read docs and understand what's going on. I'm also a BSD guy so I prefer to not patch anything until the patch is final and tested as it's better not to break things than bring new functionality in. After all I'm not the owner. For example I don't like both patches that you mentioned. First one adds one code block and tests only for the empty string. The second one has better approach but why it's checked after the cursor is created? I.e. moving the check to the beginning of the function looks better to me. If you really want to help - try making travis work. It was working, then it was broken and there are no willing victims to fix that. Another good task is to revamp data processing when working with the database. Right now everything is converted to SQL requests (strings) and then fed to the server. The good way of doing that is making source read tuples, create prepared statement for submission and optionally add filter to fix field types. This will greatly speed up the whole process. And probably yes, we need to mark a milestone as a last release was too long ago, I just wasn't too sure about the commits as I personally can't test everything thoroughly (thus I mentioned trevis at first place). Thanks for pinging me. I need to be pinged... :) |
Hi, First, thank you @kworr to answer me :-) About Travis, I can definitely help, but I need to give me admin access on py-mysql2pgsql repository and Travis. Is it possible to give me ? The roadmap I propose:
What do you think for this roadmap ? |
Did anything happen here since? Do I read correctly that I should use the git version? |
Leave here links to similar projects, to improve. Fast efficiently sync database without dumping & reloading PostgreSQL/MySQL (C++11)
mysqlcompat (SQL functions, easing migration)
|
Hi,
This tool is great, at least better than the ruby equivalent (mysql2pgsql), but I had some issues during a migration that was already fixed on other forkes, and sometimes, resolved the same bug in several forkes.
For example, the empty SQL error:
Do you need some help to close and merge interesting things to prepare a new release ?
I understand that you don't have time anymore to work on this project, I can help you, if you want.
Regards.
The text was updated successfully, but these errors were encountered: