As SQLA 2.0 seems to be available soon:
I'd like to get to know the resume that has been taken from the results of Mark's (not too unambiguos) poll "What do you want done with the newsgroup data?".
So, dear SQLA 2.0 developers, please let us know what kind of newsgroup import variant or archive site are you gonna present to us?
(No, I won't ask why...)
I know all of you are eager to learn about what we have been doing, so here is the current state of SQLA 2.0:
We have spent the last many months porting OSQA to use SQL Anywhere as its back end database (the port actually only took an hour or so since SA's django driver "just worked" :-) and making enhancements to it to be able to better serve our needs. Some of the changes that we have made are:
We have been using a version of the revised OSQA software internally for quite a few months and believe it is ready to go live.... but we need to wait for Sybase IT to do some "magic" to make the site visible to the internet.
Once SQLA 2.0 is accessible to the world we will load in the SQLA 1.0 data - i.e. this site's data - and then plan to have a period of time where the user community can try it out and give us feedback. Sometime during the beta period we will announce the date for the official switch-over to occur. On that date we will take a final dump of the SQLA 1.0 data and put it into the new SQLA 2.0 database. Note: Any data entered into the SQLA 2.0 site during the beta period will be lost.
At some later time - within a few weeks to months of SQLA 2.0 going live - we plan to load the newsgroup data into SQLA 2.0 and all SQL Anywhere related newsgroups will be changed to be read-only.
Note that I have not given any dates to when any of this is going to happen because at this time we don't know the answer to that part of the process. This community (and the newsgroup community) will be notified when we know this information and everyone will be invited to participate in the new SQLA 2.0 Q&A forum.
... so stay tuned!
To answer my particular question, I dare to quote from Mark's elaborate explanation:
That's the Migrate to SQLA (Bulk Load) approach, it seems.
answered 09 Nov '10, 20:09