SQL queries for Textpattern

gaekwad · 2014-01-18 11:48:46

Globally changing article IDs

From a recent thread on Google+, here’s a way of using the MySQL concat function to prepend a number to the article ID:

update textpattern set ID = concat('9', ID);

The 9 could be any number, and the one I used in the example. For instance, this would change a series of article IDs from 1,2,3,4,5,6,7,8,9,10 to 91,92,93,94,95,96,97,98,99,910. Note this is prepending (putting a number before the start of the ID) and not incrementing, so the numeric continuity is gone.

Last edited by Gocom (2014-01-25 15:33:02)

Gocom · 2014-01-25 15:21:44

I’ve modified some of the posts to use proper terminology and naming. The database management system is called MySQL; the language you speak of is SQL and some of you are using MySQL extensions on top of standard SQL. What you might want to make clear is that some of these queries will perform pretty badly; like for instance all those involving rand().

That said, you might want to change the title to something different since these snippets are starting to have nothing to do with SQL. Some are even using plugins. My suggestion would be to unstick these thread and post these tips on TXP Tips. I personally unfortunately don’t see much value in this thread as its now.

Last edited by Gocom (2014-01-25 15:28:35)

Gocom · 2014-01-25 15:42:48

uli wrote #278061:

Reset auto increment to a certain base value

Here an example for the txp_file table.

ALTER TABLE `txp_file` AUTO_INCREMENT = 98;...

Please note: Backup your database before running any mySQL queries.

Please note that the auto-increment ID can not be equal or less than the highest existing ID in the table. It must be n + y, where n is the highest ID in the table and y is between n + 1 and 2 ³² – (n+1)

etc · 2014-01-26 10:11:59

Gocom wrote #278489:

you might want to change the title to something different since these snippets are starting to have nothing to do with SQL. Some are even using plugins.

Given that core tags do not accept SQL queries as attributes, I don’t see how to avoid plugins… would renaming this thread Useless SQL queries be an acceptable compromise?

els · 2014-01-26 16:05:58

etc wrote #278497:

would renaming this thread Useless SQL queries be an acceptable compromise?

Lol :)

mrdale · 2014-01-27 04:32:05

Gocom wrote #278489: I personally unfortunately don’t see much value in this thread as its now.

LOL, why would you? You’re obviously not taking your first steps in SQL queries, so policing newbie’s correct usage of “mySQL” and “SQL” is a bit silly don’t you think?

I love sharing queries and have learned a lot by just seeing how people construct them. I’ve just refrained from sharing mine on this thread because most of my gems, like “show me the ballers” are specific to my custom menagerie of plugins.

uli · 2014-01-27 11:57:18

renaming this thread Useless SQL queries

correct usage of “mySQL” and “SQL”

Point taken, topic renamed, forum saved. Greets, Bert Macklin

mrdale wrote #278512:

I […] have learned a lot by just seeing how people construct them.

Exactly that was the reason for opening the topic. And by having SQL in the familiar TXP context there’s one unknown less in the equation: We know the column names.

Gocom · 2014-02-08 15:10:24

That’s what you hang on and ignore the point that this topic would better serve on TXPTips, on a site mean for tips? Legit.

You sharing copy+paste snippets doesn’t teach anyone. If yourself aren’t well educated enough to explain your snippet, at least use proper terminology so that people interested can search the reasons how and why the snippet of yours works. Lack of explaining and teaching is why I see this thread as invaluable. Not because I don’t need these snippets. Its why I want these snippets on TXPTips as longer guides, not scattered small snippets buried on this thread.

Last edited by Gocom (2014-02-08 15:22:55)

colak · 2014-02-08 17:15:50

I guess that there’s a difference between txptips and here. When posting snippets of code in this forum we post them so as to hopefully get some feedback which will help in their development. That is how I saw the “Examples” forum and this is how I see this thread.

I agree that final snippets (with explanations) should appear in txptips which it should function as our central resource. Until those snippets become final though, this forum is the best tool we have to have our ideas scrutinised.

colak · 2014-02-13 07:41:20

Here’s a simple mysql to change the password of a user. It’s handy when the server does not send emails to new users

update txp_users set pass=password(lower('pass')) where name='user';

Dragondz · 2014-02-13 08:35:05

colak wrote #278897:

Here’s a simple mysql to change the password of a user. It’s handy when the server does not send emails to new users

update txp_users set pass=password(lower('pass')) where name='user';

There is also rah_change _password that can do that.

jakob · 2014-10-02 16:36:36

I found this thread useful so I thought I’d add to it. The use case is a simple calendar of events page with start and end dates stored in custom fields rather than using txp’s own posted/expires fields:

Show only articles newer / older than the current date using dates stored in custom_fields

The setup is as follows:

uses Stef’s smd_query plugin
custom field custom_18 is the event’s start date in format YYYY-MM-DD (this date format sorts well)
custom field custom_19 is the event’s end date in format YYYY-MM-DD (with glz_custom_fields, you can set the date picker to use this date format)
event-itemis a normal txp form to display the event details using regular textpattern tags (the smd_query attribute populate="article" makes that possible – see note in example 13 in the smd_query docs).
shows both sticky and live articles

<txp:smd_query query="SELECT *,
     unix_timestamp(Posted) as uPosted,
     unix_timestamp(LastMod) as uLastMod,
     unix_timestamp(Expires) as uExpires
     FROM textpattern 
     WHERE Status IN (4,5)
     AND section = 'calendar'
     AND custom_19 >= CURDATE()
     ORDER BY custom_18 ASC
     LIMIT 5"
     wraptag="" break="" form="event_item"
     populate="article" />

This can easily be adapted for an archive page of past events by reversing the display order and changing “greater than or equal” to “less than”:

<txp:smd_query query="SELECT *,
     unix_timestamp(Posted) as uPosted,
     unix_timestamp(LastMod) as uLastMod,
     unix_timestamp(Expires) as uExpires
     FROM textpattern 
     WHERE Status IN (4,5)
     AND section = 'calendar'
     AND custom_19 < CURDATE()
     ORDER BY custom_18 DESC
     LIMIT 5"
     wraptag="" break="" form="event_item"
     populate="article" />

PS: Corrections welcome if I’ve overlooked something.

uli · 2016-05-27 14:11:07

Using image names as alt texts, removing file name extensions

In case you have neatly readable image names when you upload images to Textpattern, you can save the labour of copying their names over to the alternative text field by executing the following SQL statement:

UPDATE txp_image SET alt = name,
alt = 
REPLACE(
REPLACE(
REPLACE(
REPLACE(
REPLACE(
alt, '.jpg', '')
,'.jpeg','')
,'.png','')
,'.gif','')
,'_',' ')
WHERE alt = '';

The first line takes the DB entry from the name field and copies it over to the alt field, the following four, nested, REPLACE steps each takes one of the pixel formats’ file extensions valid in Textpattern and removes them from the alt field by replacing them with nothing (''). The last REPLACE supersedes understrikes you might have used with spaces. Finally, WHERE alt = '' shelters alt fields that already have entries.

Note: Although this should not overwrite entries you might already have in the alt fields you’d better backup your database before!

In case you know something more readable to set up than these repeated, nested, statements, please post here.

Last edited by uli (2016-05-27 14:38:58)

uli · 2022-08-11 18:25:55

Increase numeric values 2

For those with bookmarks leading here:
This post has been merged with Increase numeric values 1

Last edited by uli (2022-09-23 19:18:39)

Textpattern CMS

Textpattern CMS support forum

#16 2014-01-18 11:48:46

Re: SQL queries for Textpattern

Globally changing article IDs

#17 2014-01-25 15:21:44

Re: SQL queries for Textpattern

#18 2014-01-25 15:42:48

Re: SQL queries for Textpattern

uli wrote #278061:

#19 2014-01-26 10:11:59

Re: SQL queries for Textpattern

Gocom wrote #278489:

#20 2014-01-26 16:05:58

Re: SQL queries for Textpattern

etc wrote #278497:

#21 2014-01-27 04:32:05

Re: SQL queries for Textpattern

#22 2014-01-27 11:57:18

Re: SQL queries for Textpattern

mrdale wrote #278512:

#23 2014-02-08 15:10:24

Re: SQL queries for Textpattern

#24 2014-02-08 17:15:50

Re: SQL queries for Textpattern

#25 2014-02-13 07:41:20

Re: SQL queries for Textpattern

#26 2014-02-13 08:35:05

Re: SQL queries for Textpattern

colak wrote #278897:

#27 2014-10-02 16:36:36

Re: SQL queries for Textpattern

Show only articles newer / older than the current date using dates stored in custom_fields

#28 2016-05-27 14:11:07

Re: SQL queries for Textpattern

Using image names as alt texts, removing file name extensions

#29 2022-08-11 18:25:55

Re: SQL queries for Textpattern

Increase numeric values 2

Board footer