regular expressions frage

[roflnub]

Hi, wie kann ich mir regular expressions in einem langen Text nach dem 4 Punktzeichen suchen. Ich will jeden Text den ich habe auf die ersten vier Sätze kürzen. danke.

 

[Gumbo]

^(?:[^.]*\.){,4}

 

[roflnub]

hey danke

aber iregendwie funktioniert das nicht

<?php

$str = "So what we are going to do is make a separate table called and in this, we will store all the information we need from the author - such as emails, URLs, their name, and a unique ID. Then in our blog post table we will point to the person we want using that person's unique ID. This id is referred to as a foreign key and the relationship between the blog post table and the people table is called a one-to-many relationship.

One other thing we want to have in our blog is a tag for each blog post. Again we want to make our database efficient so we will create a separate table for our tags. Now what do we do? Should we create a field in the blog post table that is a foreign key for our tag? The problem with using a one-to-one relationship this time is sometimes blog posts have more than one tag; so again, we will use a one-to-many relationship. To do this we need to create another table that will be called something like that will hold two foreign keys, one will be the blog post's ID and the other will be the tag ID that the blog post is associated with. This way we can assign as many tags as we want to a blog post but can still edit the information about that specific tag across all posts with a simple MySQL query.

Now that we have outlined what we want our database to look like, let's create it. I'll be using PhpMyAdmin since that is the most widely used MySQL admin client. There are a few different naming conventions you can use when creating your database, table, and field names. I personally like to use all lowercase and underscores in place of spaces.";

preg_match_all("/^(?:[^.]*\.){,4}/", $str, $a);
print_r($a);

?>

 

[Fide]

Hi,

<?php

$str = "So what we are going to do is make a separate table called and in this, we will store all the information we need from the author - such as emails, URLs, their name, and a unique ID. Then in our blog post table we will point to the person we want using that person's unique ID. This id is referred to as a foreign key and the relationship between the blog post table and the people table is called a one-to-many relationship.

One other thing we want to have in our blog is a tag for each blog post. Again we want to make our database efficient so we will create a separate table for our tags. Now what do we do? Should we create a field in the blog post table that is a foreign key for our tag? The problem with using a one-to-one relationship this time is sometimes blog posts have more than one tag; so again, we will use a one-to-many relationship. To do this we need to create another table that will be called something like that will hold two foreign keys, one will be the blog post's ID and the other will be the tag ID that the blog post is associated with. This way we can assign as many tags as we want to a blog post but can still edit the information about that specific tag across all posts with a simple MySQL query.

Now that we have outlined what we want our database to look like, let's create it. I'll be using PhpMyAdmin since that is the most widely used MySQL admin client. There are a few different naming conventions you can use when creating your database, table, and field names. I personally like to use all lowercase and underscores in place of spaces.";

preg_match_all("/^(?:[^.]*\.){0,4}/", $str, $a);
print_r($a);

?>

oder:

<?php

$str = "So what we are going to do is make a separate table called and in this, we will store all the information we need from the author - such as emails, URLs, their name, and a unique ID. Then in our blog post table we will point to the person we want using that person's unique ID. This id is referred to as a foreign key and the relationship between the blog post table and the people table is called a one-to-many relationship.

One other thing we want to have in our blog is a tag for each blog post. Again we want to make our database efficient so we will create a separate table for our tags. Now what do we do? Should we create a field in the blog post table that is a foreign key for our tag? The problem with using a one-to-one relationship this time is sometimes blog posts have more than one tag; so again, we will use a one-to-many relationship. To do this we need to create another table that will be called something like that will hold two foreign keys, one will be the blog post's ID and the other will be the tag ID that the blog post is associated with. This way we can assign as many tags as we want to a blog post but can still edit the information about that specific tag across all posts with a simple MySQL query.

Now that we have outlined what we want our database to look like, let's create it. I'll be using PhpMyAdmin since that is the most widely used MySQL admin client. There are a few different naming conventions you can use when creating your database, table, and field names. I personally like to use all lowercase and underscores in place of spaces.";

preg_match_all("/^(?:[^.]*\.){4}/", $str, $a);
print_r($a);

?>

Es geht nicht einfach ",4" in den Geschweiftenklammern. (die 4 steht für 4 Sätze, wenn nur eine 4 drin steht müssen es genau 4 sein, wenn da z.B. 0,4 drin steht, dann gehen 0-4 Sätze)

mfg.Fide