New Database Model ZXDB

[PeterJ]

Thanks @Einar Saukas,

A very elegant solution. Peter

[Einar Saukas]

A new ZXDB update is now available!

[Einar Saukas]

Another ZXDB update is available!

[Einar Saukas]

A new ZXDB update is available!

According to the plan announced a few updates ago, this update removed columns "magazines.label_id" and "magazines.label2_id". Tables "aux_issues" and "aux_origintypes" were removed too. Therefore if you have a site or application that's using ZXDB, I recommend making the required changes before applying this update.

Check my previous post for further details, or contact me if you have any questions!

[Einar Saukas]

Another ZXDB update is now available!

This version includes a HUGE update in magazine references, including a lot more reviews from the latest ZXSR release. Many thanks to @Vampyre for all his hard work!

[Einar Saukas]

Yet another ZXDB update is available!

[Einar Saukas]

Another ZXDB update is now available!

[Einar Saukas]

A new ZXDB update is already available!

[Einar Saukas]

Another ZXDB update is available!

[Einar Saukas]

A new ZXDB update is now available!

[Einar Saukas]

Another ZXDB update is available!

[Einar Saukas]

A new ZXDB version is now available!

[Einar Saukas]

Yet another ZXDB version is available!

[PeterJ]

Thanks @Einar Saukas. I will update the website on Tuesday.

[Einar Saukas]

A new ZXDB release is available!

[Einar Saukas]

Yet another ZXDB version is available!

This is a fairly large update, adding quite a few magazines and over a thousand type-ins...

[Einar Saukas]

Another ZXDB version is available!

It contains another 500 type-ins from our ongoing work to integrate with Type Fantastic.

Also if you have a web site or application using ZXDB, please read this:

• Fields "magazines.original_price" and "magazines.republish_price" still exist, but they are not used anymore. They came from Martijn's old WoS and, despite their names, they actually stored the minimum and maximum prices of a certain magazine. However this information wasn't accurate. Instead of them, there are now new fields "issues.price" and "issues.currency_id" that store the release price of each individual magazine issue.

• These old fields "magazines.original_price" and "magazines.republish_price" will be removed in the next ZXDB update. I doubt anyone is using them anyway.

[PeterJ]

Thanks @Einar Saukas,

I will update after the Bank Holiday.

Whilst it's great to have all these type ins, disappointingly we don't have any screenshots or program files for these.

If forum members fancy helping us out, please upload via the preservation tools. Most are available from Type Fantastic in one form or another. There is a ZX81 screen converter in the preservation tools.

[Einar Saukas]

A new ZXDB release is now available!

[Einar Saukas]

Another ZXDB version is now available!

Also if you have a web site or application using ZXDB, please read this:

• Column "entries.hide_from_stp" still exists, but it's not used anymore. This was an internal flag to help integrate Martijn's old WoS with Spectrum Tape Preservation. However this information wasn't deleted, it's now simply stored in a different way using groups/tags. This column "entries.hide_from_stp" will be removed in the next ZXDB update. I'm sure nobody is using it nowadays anyway!

[PeterJ]

Thanks @Einar Saukas,

I will do the update on Thursday afternoon.

Peter

[Einar Saukas]

A new ZXDB update is available!

[PeterJ]

Thanks @Einar Saukas,

As the size of the SQL file is getting larger, I was wondering if it would be possible to provide cumulative updates. Obviously, if this is extra work for you don't bother.

[Einar Saukas]

Unfortunately it won't help. Some of the scripts I run when preparing each new release (to reimport Speccy Maps, ZXSR, etc) take longer than reloading the entire database.

EDIT: There are database comparison tools like DBDiff you could try. When it's time to update SpectrumComputing, instead of reloading the entire database in the server, you could reload it in your local computer, generate a diff from the server, then apply the diff to the server. This process would also take care of any possible changes previously applied directly to the server from the online forms... At least that's the theory. I have no idea how reliable is this tool. Does anybody have experience using it, or any of the other similar tools?

[Einar Saukas]

A new ZXDB update is now available!

Also if you have a web site or application using ZXDB, please read this:

• Column "entries.mag_ratings" will be removed in the next update. This column was imported from Martijn's old WoS, storing a simplified representation of the main review scores obtained by each program. Since ZXDB is now fully integrated with ZXSR and contains all detailed scores, these simplified (sometimes innacurate) scores are not useful anymore. I highly doubt anybody ever used this information anyway.