Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

You have convinced me about dropping the XML approach. I spent a while thinking about the inner platform and you are right, that is what I am doing here. I initially thought you were referring to what the end users had access to as far as creating tables so was a little confused but a weekend and some beers has helped me understand. I had never thought about create creating a distinct table for each. It would make things much easier when displaying the data too. Thanks.

Goose
– Goose

2014-08-26 12:37:04 +00:00
Commented Aug 26, 2014 at 12:37

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »