By scoby on

I'm actually moving from drupal to wordpress
but I thought this was the most appropriate forum

I have been using the path and pathauto on my drupal blog

I'm now migrating to a wordpress install and I'm trying to make sure my urls stay the same.

Fro what I can see the url_alias table holds the slug that the user sees in the url in the dst field
my-blog-post
and this points to the internal src
node/1

It seems that the dst field is exactly what I want to copy into the wordpress post_name field as this gets used to generate the slug in wordpress.
Copy the values that are there already and the urls are guaranteed to remain the same, right?

The url_alias table only has one more field which is pid and I can't for the life of me see how this relates to the node.

I need to get the node text, title and the url_alias dst field with a select statement.

Sorry for the noobness, can anyone point out how these link together?

Thanks :)

⋅ Categories: Drupal 5.x

Comments

HyperD’s picture

HyperD commented

I have a similar problem, I don't know in what manner drupal corelat url_alias with the real address and the nodes ... but noticing that is almost one year that you asked this and noboy answered, I think to have few chances to get a real useful answer here or somewhere else ... that's pity ...
Tiziano

SolutionFactor’s picture

SolutionFactor commented

Similar problem here too. Does anyone have an answer?

On a related note, I'm suprised at the lack of proper db design in open source apps. Following best practices, such as using integrity constraints (ie. foreign keys) would result in not just a higher quality app, but also in a reduction of questions/problems such as this. If foreign keys were in place we could simply view the table's definition and find this out...relations would be self documented. Instead, users and developers are forced to research such answers.

Can any Drupal developers speak as to why foreign keys were left out of the database? ... just curious.

Thanks guys.