Hi There,

I'm wanting to commmence a site migration project to Drupal, and I have tagged the links package to be used to handle embedded links and weblinks. I realise that the links package is still under development, but I was wondering if the database structure is complete yet? If there are no more changes to be made to the database structure then I can start my migration, if more changes are likely then I'll probably need to look at another solution.

Cheers

Comments

Bèr Kessels’s picture

Eventhough we (obviously) cannot make guarantees, It is definately safe to use this module/bundle.

The database scheme might change, in future, but that will not affect you at all. If you develop modules, and use the APIs we will take care of your module not breaking. Same goes for any data: If you use the bundle, and somehting may change, there will be upgrade paths available. After all: our data is in that structure too, and we don't want that to break (scratching own itches, so to say).

If this answered your question, could you please mark this closed?

Bèr

brashquido’s picture

Status: Active » Closed (fixed)

Yep, good enough for me. Thanks Bèr.

syscrusher’s picture

Assigned: Unassigned » syscrusher
Priority: Critical » Normal
Status: Closed (fixed) » Active

The database structure is essentially stable at this time, *except* for the monitoring table which should be thought of as a rough design. The {links} and {links_node} tables are committed to be either (1) stable, or (2) automatically upgradeable using the new Drupal install feature. In other words, you can safely migrate data into the existing structure of these two tables and rely on it being auto-upgraded if necessary in the future. Frankly, changes to the database schema of these tables are extremely unlikely for the near term.

One word of caution: There are very specific expectations in the API about the semantics of various fields and the relationships between the tables. I strongly urge you to use the links API to add or modify data in these tables, rather than going to direct SQL. If you do use direct SQL, I can't commit that the API will work correctly with your data records. There's a fairly extensive set of documentation with the module in the text files; you should read that before you develop your migration code. Also take a look at the existing migration PHP scripts in the module's directory for examples of tested and working code. That may save you some time.

By the way, the API is stable as far as upward-compatibility goes (that is, I won't be taking anything away that's there now), but I am still willing to consider additional API functions if a good case can be made for the need. The statistics functions in the API now will be expanded in the future.

Please let me know if this doesn't answer your question.

Kind regards,

Scott

syscrusher’s picture

Status: Active » Closed (fixed)
syscrusher’s picture

(nota bene -- sorry for the duplication of Ber's reply. I didn't get the notification of that until after I posted mine)