Bug #1096 (closed)
Opened 11 years ago
Closed 11 years ago
SQL scripts broken under Windows
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | blocker | Cc: | m.porter@…, cxallan |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description (last modified by jmoore)
Running ant setup-db under Windows with the OMERO3A__11 scripts hangs during import of ddl.sql. This is most likely caused by platform-based line-endings large files due to the changes from r2783.
Change History (2)
comment:1 Changed 11 years ago by jmoore
comment:2 Changed 11 years ago by jmoore
- Description modified (diff)
- Resolution set to fixed
- Status changed from new to closed
Michael confirmed that the fix completes on his box. Closing.
Unforunately, I couldn't find information on why this was happening
particularly, so we may need to revisit. Probably the best bet is to
run setup-db on Windows in each build, and count and overly long
build time as a failure.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
r2797 will hopefully clear this up.
The problem isn't line-endings as originally thought, but some form of internal batch size in Postgres on Windows. Breaking up the schema.sql (a.k.a. ddl.sql) with more ';;' delimiters allows the execution to continue normally.
I've added delimiter=";;" to the schema generation so we shouldn't have to worry about this anymore.
Needs a bit more testing though.