hazaar/hazaar-dbi
1
0
Fork 0
Code Issues Pull requests Projects Releases 8 Packages Wiki Activity Actions

Data sync runs but has no affect on PGSQL db migration #8

New issue
Closed
opened 2017-01-27 09:58:43 +00:00 by jamie · 6 comments
jamie commented 2017-01-27 09:58:43 +00:00 (Migrated from git.hazaar.io)
Copy link

Everything seems to work. I have even stepped through the code and it executes the syncSchemaData() method but it appears to have no affect as there are no rows in the tables.

Everything seems to work. I have even stepped through the code and it executes the syncSchemaData() method but it appears to have no affect as there are no rows in the tables.
jamie commented 2017-04-01 00:07:01 +00:00 (Migrated from git.hazaar.io)
Copy link

added ~160 label

added ~160 label
jamie commented 2017-06-22 04:22:44 +00:00 (Migrated from git.hazaar.io)
Copy link

I don't thinks this is a problem anymore for some reason. I just did a test program and it sync'd my table records. I have also noticed that my live production application now appears to be working as well.

I don't thinks this is a problem anymore for some reason. I just did a test program and it sync'd my table records. I have also noticed that my live production application now appears to be working as well.
jamie commented 2017-06-22 04:22:45 +00:00 (Migrated from git.hazaar.io)
Copy link

closed

closed
jamie commented 2017-07-14 02:12:38 +00:00 (Migrated from git.hazaar.io)
Copy link

This is an issue on a new schema, by the looks of it. If it's migrating up, then it's ok. If it's a fresh schema then I don't think the data sync is running, or it is not having any affect.

This is an issue on a new schema, by the looks of it. If it's migrating up, then it's ok. If it's a fresh schema then I don't think the data sync is running, or it is not having any affect.
jamie commented 2017-07-14 02:12:39 +00:00 (Migrated from git.hazaar.io)
Copy link

reopened

reopened
jamie commented 2017-07-25 02:34:54 +00:00 (Migrated from git.hazaar.io)
Copy link

closed via commit f4a1fae3ab

closed via commit f4a1fae3ab7a00cfd05182de4d77a72f121ccbc9
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
1.4-develop
1.3-develop
release-2.3.1
release-2.3.0
release-2.2.5
release-2.2.4
release-2.2.3
release-2.2.2
release-2.2.1
release-2.2.0
release-2.1.0
release-2.0.3
release-2.0.2
release-2.0.1
release-1.4.1
release-1.3.2
release-2.0.0
release-1.4.0
release-1.3.1
release-1.3.0
release-1.2.11
release-1.2.10
release-1.2.9
release-1.2.8
release-1.2.7
release-1.2.6
release-1.2.5
release-1.2.4
release-1.2.3
release-1.2.2
release-1.2.1
release-1.2.0
release-1.1.9
release-1.1.8
release-1.1.7
release-1.1.6
release-1.1.5
release-1.1.4
release-1.1.3
release-1.1.2
release-1.1.1
release-1.1.0
release-1.0.8
release-1.0.7
release-1.0.6
release-1.0.5
release-1.0.4
release-1.0.3
release-1.0.2
release-1.0.1
release-1.0.0
Labels
Clear labels   
bug

   
confirmed

   
critical

   
discussion

   
documentation

   
Doing

   
enhancement

   
suggestion

   
support

   
To Do
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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#8
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?