search

google-code-export / ords

Automatically exported from code.google.com/p/ords
1 stars 0 forks source link

Email reporting on database upload says that it was both unsuccessful and successful #480

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Upload a db to ORDS (it was an invalid SQL db that generated this oddity)
2. Receive an email saying "Ooops! There has been a problem and your database 
(wview-history_20140727_010544.sql) has not been imported into ORDS. The error 
reported was Success"
3.

What is the expected output? What do you see instead?
'Success' is not a very helpful error message! And could we please lose the 
initial 'Ooops!' - it's going to start to grate on our users pretty swiftly.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by jajwil...@gmail.com on 28 Jul 2014 at 10:28

GoogleCodeExporter commented 9 years ago 
Please attach the offending database

Original comment by thest...@gmail.com on 28 Jul 2014 at 10:36

GoogleCodeExporter commented 9 years ago 
I have removed the word "Ooops!". Shame ...

Original comment by thest...@gmail.com on 28 Jul 2014 at 10:38

GoogleCodeExporter commented 9 years ago 
This was the one that Mike Fraser tried to upload. I'll keep pestering him
for a copy.

Original comment by jajwil...@gmail.com on 28 Jul 2014 at 10:59

GoogleCodeExporter commented 9 years ago 
I have now emailed you a couple of example SQL databases, so passing this back 
to you.

Original comment by jajwil...@gmail.com on 28 Jul 2014 at 3:54

GoogleCodeExporter commented 9 years ago 
This is the db Mike tried to upload. It may well have failed due to being 
invalid SQL - but it's really the error message that needs to be fixed before 
go-live, not the file upload

Original comment by jajwil...@gmail.com on 31 Jul 2014 at 9:16

Attachments:

GoogleCodeExporter commented 9 years ago 
I have removed this error reported. Due to the fact we are hours away from 
go-live I don't want to put a more detailed fix in. 

Essentially, I have fixed the user-problem but it would be nice if a valid 
error was sent to the user.

Please re-raise and I shall look at this after go-live.

Original comment by thest...@gmail.com on 31 Jul 2014 at 9:42