Any developers up? Questions about XML

[Young]

Working on a project. It will have about 1,500-2,000 separate entries with about 10 fields per entry. There won't be a huge amount of queries at first but scalability is a concern for the future. XML is a necessity.

1. Should I go with an XML file or a Database?
1a. Straight XML or MySql with XML export?
2. Anyone want to give me any advice or pointers on the way that you would do it.

[ilbb]

1) Save data in your MySQL
2) Cache your xml file

[GrouchyAdmin]

1) You have got to be kidding.
2) You need more experience; If I were you, I'd start reading up on database design.

[brandonstills]

Need more information before we can give you a suggestion. The nature of the data sounds like it's tabular in nature. Why is XML required? Data are data.

[Young]

Need more information before we can give you a suggestion. The nature of the data sounds like it's tabular in nature. Why is XML required? Data are data.

Data needs to be portable across different platforms + apps (online and off)

[Young]

1) You have got to be kidding.
2) You need more experience; If I were you, I'd start reading up on database design.

1. No I'm not kidding.

2. You have no clue how much experience I have with MySQL. I don't know much about XML. I am still learning.

3. You didn't answer my question. You contributed zero. So why waste your time? You'll never get those 2 minutes of your life back.

[Young]

1) Save data in your MySQL
2) Cache your xml file

Thanks this is the way I think I'm gonna go. Though I'm reading up on some opensource XML databases.

[GrouchyAdmin]

You contributed zero. So why waste your time? You'll never get those 2 minutes of your life back.

Neither will you manage to write a viable, useful application without knowing what the fuck you're doing, but don't let me stop you - I'll take the 'we need this rebuilt' job when you're gone.

[mrkris]

I would store the data in the database, then assuming you have an ORM approach, have a to_xml method that will convert the record object into xml.

[Young]

Neither will you manage to write a viable, useful application without knowing what the fuck you're doing, but don't let me stop you - I'll take the 'we need this rebuilt' job when you're gone.

It's my app you dumb fuck.

So I take it you were just born with the ability to design databases? You didn't learn right? God you are fucking moronic.

[Sands]

Pipe delimited text files. That's the way to go

[Young]

Pipe delimited text files. That's the way to go

Really?!?!? AWESOME! Starting on it now.

[Young]

I would store the data in the database, then assuming you have an ORM approach, have a to_xml method that will convert the record object into xml.

This is the approach I think I'm going to take. Thanks. All I wanted to know. Instead I get a couple of responses from smart asses who need the work.

[mrkris]

It's my app you dumb fuck.

So I take it you were just born with the ability to design databases? You didn't learn right? God you are fucking moronic.

Although I can understand your frustrations, Grouchy is by far one of the most intelligent people on GFY when it comes to technology. Yes, a sarcastic dick face, but still intelligent.

[GrouchyAdmin]

Although I can understand your frustrations, Grouchy is by far one of the most intelligent people on GFY when it comes to technology. Yes, a sarcastic dick face, but still intelligent.

Fuck you too, skittle-popping nancy boy.

[mrkris]

Fuck you too, skittle-popping nancy boy.

You're the idiot who thought they were M&Ms

[GrouchyAdmin]

You're the idiot who thought they were M&Ms

All I know I saw you taking them out of Brandon's He-Man lunchbox.

[Bird]

Use your database and user other sites XML feeds.

only use xml from your DB if your providing for widgets or API's

[GrouchyAdmin]

rss2xml.php3

[mrkris]

Use your database and user other sites XML feeds.

only use xml from your DB if your providing for widgets or API's

You're silly.

[jay23]

Working on a project. It will have about 1,500-2,000 separate entries with about 10 fields per entry. There won't be a huge amount of queries at first but scalability is a concern for the future. XML is a necessity.

1. Should I go with an XML file or a Database?
1a. Straight XML or MySql with XML export?
2. Anyone want to give me any advice or pointers on the way that you would do it.

These 10 Fields per entry, are they going to be same for all the entry or different.

1. If its same, go with any SQL data base
2. If its differnt then go with a XML data base (I personaly use MS SQL 2008 and its XML support)

Jay

[Linguist]

1. No I'm not kidding.

2. You have no clue how much experience I have with MySQL. I don't know much about XML. I am still learning.

3. You didn't answer my question. You contributed zero. So why waste your time? You'll never get those 2 minutes of your life back.

Sorry mate but I totally agree with Grouchy here, and whether or not you use database or xml file depends purely on how you design the database. In this project a shitty database design will be about as fast or slower than the xml file.