Hi,
I have a bit of a DB design question, associated with postgresql in
particular, hopefully thinking it could solve my dilemma.
This is my setup of 3 tables:
Table_1
id_t1
name
date_of_discovery
history
Table_2
id_t2
name
type
size
Table_3
id_t3
name
location
color
I want a solution (table
Hi,
Is there anything like MySQL workbench for PostgreSQL?
I know there are a few alternatives, but was hoping to hear specific choices
and not just some random anonymous internet list like the ones i have been
reading.
What i need is something powerful enough to connect to an existing
PostgreSQ
, that maybe
will allow me to plug to the Flex side of the interface.
Again, than you all for the great information.
MV
On Fri, Aug 20, 2010 at 12:09 PM, Eduardo wrote:
> On Thu, 19 Aug 2010 20:35:50 +0100
> Miguel Vaz wrote:
>
> > Hi,
> >
> > I need to make a
Hi,
I need to make a database of books. Several specific subject books that are
to be searchable.
Is it viable to have the complete book text on a database and search inside
it? Or should i consider keeping only its metadata (name, author, filename,
etc) on the DB, keep the book file on the HD an
10 at 7:16 PM, Tim Landscheidt wrote:
> Miguel Vaz wrote:
>
> > Thank you for the opinion, Alban. The names are the least of my worries,
> i
> > typed them without thinking. And its portuguese. :-)
>
> > If, using that design, i had a different table with something
he corresponding table of that specific type. I understand its a bit
ungrateful for you guys to understand what i mean, considering that i am
probably making things even more confusing. :-)
Pag
On Fri, Jul 9, 2010 at 1:47 PM, Tim Landscheidt wrote:
> Miguel Vaz wrote:
>
> > I was
e specific fields so there are
no empty columns on the table if i put everything in the same table.
Pag
On Fri, Jul 9, 2010 at 10:30 AM, Tim Landscheidt wrote:
> Miguel Vaz wrote:
>
> > [...]
> > * sites (generic):
>
> > id_site
> > name
> > description
&g
Hi,
I am having some uncertainty while designing the following structure:
I have two sets of data:
* arqueology sites (can be natural):
id
name
description
id_category
id_period
x
y
* natural sites (can be arqueological also - bear with me -, so there will
be duplicate records in the above t
