Pgloader could not parse subexpression when parsing

On the code cleaning front, some refactoring did take place. Plenty things are worthy of some notes, let's focus on the main themes found in the 179 commits in between pgloader 3.

Sign in to view. START 0: MAIN [cleanup] 13: We don't have an option to specify the encoding of a database at this point, even when the database is a SQLite file. View open issues 53. When I do following command: You can also tweak the default amount of memory that the pgloader image will allow itself using when running through your data don't ask for more than your current RAM tho: Users of MS SQL will appreciate a lot of bug fixes and improvements to the coverage of their source database.

This score is calculated by counting number of weeks with non-zero issues or PR activity in the last 1 year period.

Issues filed for dimitri/pgloader

Development snapshot again git hash fecae2c. Thanks to all users who report use cases and bugs and open issues! Dear pgloader developer!

The versioning is now following the Emacs model, where any X. Stack Overflow works best with JavaScript enabled.

Common Lisp. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. This works: This new release brings stability on the table.

This score is calculated by counting number of weeks with non-zero commits in the last 1 year period. Sign in to comment.

The default PostgreSQL behaviour is transactional, which means that any erroneous line in the input data file or remote database will stop the entire bulk load for the table.

You can install pgloader directly from apt. Here's the config file I used should I open a separate issue? Sign up or log in Sign up using Google. This works:.