*one table* search? (there are no
joins, and will never be). I think it should, but: what do you think?
Ildefonso.
On Tue, Aug 17, 2010 at 9:51 PM, Jose Ildefonso Camargo Tolosa
wrote:
> Hi!
>
> I'm analyzing the possibility of using PostgreSQL to store a huge
> amount of data (
Hi!
I'm analyzing the possibility of using PostgreSQL to store a huge
amount of data (around 1000M records, or so), and these, even
though are short (each record just have a timestamp, and a string that
is less than 128 characters in length), the strings will be matched
against POSIX Regular E
On Wed, Aug 11, 2010 at 8:09 AM, Peter Eisentraut wrote:
> On tis, 2010-08-10 at 22:21 -0430, Jose Ildefonso Camargo Tolosa wrote:
>> And it works, it gives me something like:
>>
>> product_id | name | code | manufacturer_id |
>> manufactu
Greetings!
First: This is working, I just need a clarification on concept, so, it
is not necessary for you to look deeply at the SQL statement.
I have this:
Table: products that references manufacturer via
products.manufacturer_id to manufacturer.id (not important, just
informative).
Table: prod