hazaar/hazaar-dbi

Snapshot commits new schema version despite write failure #48

New issue

Closed

opened 2020-03-26 23:05:14 +00:00 by jamie · 4 comments

jamie commented

2020-03-26 23:05:14 +00:00

(Migrated from git.hazaar.io)

Doing a DBI snapshot, if the system can't write the migration and/or schema file due to permissions, we don't handle this error very well. The schema Version is still updated in the database, which is non-consistent. Also nothing is shown on the interface to indicate as the error is thrown in the background.

Doing a DBI snapshot, if the system can't write the migration and/or schema file due to permissions, we don't handle this error very well. The schema Version is still updated in the database, which is non-consistent. Also nothing is shown on the interface to indicate as the error is thrown in the background.

jamie commented

2020-04-01 04:34:16 +00:00

(Migrated from git.hazaar.io)

created merge request !23 to address this issue

created merge request !23 to address this issue

jamie commented

2020-04-01 04:34:16 +00:00

(Migrated from git.hazaar.io)

mentioned in merge request !23

mentioned in merge request !23

jamie commented

2020-04-01 05:56:04 +00:00

(Migrated from git.hazaar.io)

closed via merge request !23

closed via merge request !23

jamie commented

2020-04-01 05:56:04 +00:00

(Migrated from git.hazaar.io)

mentioned in commit 44a387f4f3

mentioned in commit 44a387f4f37650d4edf462eb3a75323c55101459

Sign in to join this conversation.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-dbi#48

No description provided.