: How to fix awkward "sufficiently... that..." sentence structure? I have written the following sentence, but I am dissatisfied with its construction. In particular, the that joining the two parts
I have written the following sentence, but I am dissatisfied with its construction. In particular, the that joining the two parts of the sentence reads somewhat awkwardly. Can anyone suggest a better construction for this sentence which preserves the meaning intact? Thanks in advance.
The database layout is sufficiently similar across source data formats that
we can write a single SQL query to export each output data format.
A brief background follows. The source data is imported into the database. Then the output data is exported from the database. The point of the sentence is that there is essentially the same database layout for all import formats, so it suffices to have one function for each export format. On the other hand, if the database layout depended on the import format, then one would have to have a function that depended on both the database layout and the export format. Note that "essentially the same database layout" is vague, so I'd prefer not to use that in the actual sentence. I'm just writing that in a attempt to elaborate. "Sufficiently similar" or something like that better captures the meaning, I think.
UPDATE: I've gone with
The database export functions need not depend on the source format,
since the database layout is sufficiently independent from the source
format. Therefore the data export for each output format can be
implemented as a single SQL query.
based on Standback's answer. I put the "sufficiently independent" in the second clause, because it seemed more natural in this case. I'm not sure if there is any rule to say which way around it should go. The repetition of "source format" is a little awkward, but no big deal. I think this is an improvement on my original formulation. Thanks to Standback and the others who replied.
More posts by @Ann1701686
: Is it acceptable to mix how you address the reader in an instructional Wiki? I'm working on a Wiki article that explains to new developers how our product life-cycle works. Originally, my goal
: What genre is my writing? I'm working on a couple pieces that take place in imaginary worlds. They involve made-up cities, countries, rivers, history, etc. However, the level of technology and
2 Comments
Sorted by latest first Latest Oldest Best
Here's a simple reformulation which breaks you out of the structure you dislike:
Since the database layout is sufficiently similar across all source data formats, we can write a single SQL query to export each output data format.
You could also rephrase for clarity, if you feel the original isn't clear enough. This probably requires some expansion, to make sure to get in all the details and reasoning that you consider both (a) crucial and (b) not necessarily obvious to the reader.
Since the database layout is sufficiently independent from the source data format, our export format need not rely on the original source format. Therefore, the implementation of each export format requires only a single SQL query.
The database layout is sufficiently similar across source data formats that we can write a single SQL query to export each output data format.
The data structure of the database will allow the use of a single SQL query to access the data for output and reports.
Terms of Use Privacy policy Contact About Cancellation policy © selfpublishingguru.com2024 All Rights reserved.