Srikanth Kata wrote on 02.07.2010 14:24:
When i am executing this query, i am facing the
select
s.*,a.actid,a.phone,d.domid,d.domname,d.domno,a.actno,a.actname,p.descr as
svcdescr from vwsubsmin s
inner join packages p on s.svcno=p.pkgno
inner join account a on a.actno=s.actno
inner join ssgdo
Hi,
To get column names only
select column_name from information_schema.columns where
table_name='captor_prime_aggregates';
Thanks
Sreelatha
On Wed, Jul 7, 2010 at 2:44 PM, Viktor Bojović wrote:
> \d tableName
>
>
> On Wed, Jul 7, 2010 at 11:08 AM, venkat wrote:
>
>> Dear All,
>>
>>How to
Use:
\d tablename
On Wed, Jul 7, 2010 at 3:08 PM, venkat wrote:
> Dear All,
>
>How to get Column Names from Table in PostgreSQL.
>
> Thanks and Regards,
>
> Venkat
>
When i am executing this query, i am facing the
select
s.*,a.actid,a.phone,d.domid,d.domname,d.domno,a.actno,a.actname,p.descr as
svcdescr from vwsubsmin s
inner join packages p on s.svcno=p.pkgno
inner join account a on a.actno=s.actno
inner join ssgdom d on a.domno=d.domno
in
Joe Conway schrieb:
I am the only developer, DBA etc.. for a small project. Today (yesterday was
everything was perfect) many of the sequence numbers fell behind what is the
actual PK value. For example the invoice PK sequence current value = 1056
but the table PK was 1071. Nobody (other t
On 08/07/10 2:27 PM, Dmitriy Igrishin wrote:
Hey all,
Is there a way to add constraint to the domain that used by a composite type
that used by a table? E.g.:
Currently in PG, adding constraint on Domain, which is already in use is
not supported.
CREATE DOMAIN superid AS integer;
CREATE T
On 7/7/2010 5:41 PM, John wrote:
> On Wednesday 07 July 2010 03:14:40 pm Justin Graf wrote:
>
>> I would be looking at the log files for the Inserts into that table as a
>> means to track down what is the cause. If there are no log files or
>> don't have enough detail, crank up the logging lev
Hey all,
Is there a way to add constraint to the domain that used by a composite type
that used by a table? E.g.:
CREATE DOMAIN superid AS integer;
CREATE TYPE idtype AS
(
id superid
);
CREATE TABLE mytab (id idtype NOT NULL);
ALTER DOMAIN superid ADD CONSTRAINT superid_check CHECK (VALUE >
On 07/08/10 11:38, Dave Page wrote:
On Thu, Jul 8, 2010 at 8:31 AM, silly sad wrote:
On 07/07/10 18:35, Justin Graf wrote:
On 7/7/2010 12:00 AM, silly sad wrote:
On 07/06/10 21:52, Justin Graf wrote:
I wrote an article covering this on the wiki
http://wiki.postgresql.org/wiki/BinaryFiles
On Thu, Jul 8, 2010 at 8:31 AM, silly sad wrote:
> On 07/07/10 18:35, Justin Graf wrote:
>>
>> On 7/7/2010 12:00 AM, silly sad wrote:
>>>
>>> On 07/06/10 21:52, Justin Graf wrote:
>>>
I wrote an article covering this on the wiki
http://wiki.postgresql.org/wiki/BinaryFilesInDB
>
Quoth jo...@jfcomputer.com (John):
> On Wednesday 07 July 2010 03:14:40 pm Justin Graf wrote:
> > I would be looking at the log files for the Inserts into that table as a
> > means to track down what is the cause. If there are no log files or
> > don't have enough detail, crank up the logging leve
On 07/07/10 18:35, Justin Graf wrote:
On 7/7/2010 12:00 AM, silly sad wrote:
On 07/06/10 21:52, Justin Graf wrote:
I wrote an article covering this on the wiki
http://wiki.postgresql.org/wiki/BinaryFilesInDB
there are some "red flags" in communication
(particularly reading papers)
one of th
12 matches
Mail list logo
