ohager
with the new release 3.8.1 we figured out that now `generate_scoop` may take a significant amount of time while syncing... But as @deleterium said: If there's no real performance gain...
The status is a computed value and not inside the database.... so, 1. filtering on db level is not possible 2. pagination is partially an issue....in the sense that page...
So, you potentially want to check, if something is burnt? :fire: I have a potential solution: If recipient Id = 0 we set a flag `burnt=true`, so no compatibility issue...
will be done finally There will be images for: - mainnet: H2, MariaDB, PostgreSQL - testnet: H2, MariaDB, PostgreSQL and also pre-release versions of it
exactly...as you can see in #774 I'm using build args now. The Docker Images will be provided soon. And then the action for pre-release will be added also, so somehting...
``` org.jooq.exception.DataAccessException: SQL [insert into "at" ("id", "creator_id", "name", "description", "version", "csize", "dsize", "c_user_stack_bytes", "c_call_stack_b ytes", "creation_height", "ap_code", "height", "ap_code_hash_id") values (-8117348957869510853, -8967851349279777535, 'Test', ' янв 21 18:58:04 explorer java[577504]:...
Will consider this on current iteration...
My PR was merged by Blago 15 days ago. I think you are referencing to this update. I got the code running on Visual Studio 2013, but needed to adjust...
Considering the effort to make this configurable during setup, I tend to not implement this feature directly, _but_ if we could pass parameters on startup (skipping the questions), it should...
AWESOME! btw: I'm working on a nanoflux react binder for easier integration. It'll be like redux-react, but also for multiple stores and optional action binding. I'll inform you when first...